Re: Jenkins Team

Hi Eric,

Domen and I created a buildout recipe to pull, push and trigger remote 
Jenkins jobs during the Plone Konferenz sprint in Munich:

http://pypi.python.org/pypi/collective.recipe.jenkinsjob

This makes it a lot easier to experiment with different Jenkins job 
configurations and allows us to store the job configurations in the 
buildout.coredev repo and push them to jenkins.plone.org.

I already tested the functionality here:

https://jenkins.plone.org/job/Plone42-Experimental/?

As the next step, I think we should pull the existing Plone 4.2 jenkins 
jobs (build, test, static code analysis) into the buildout.coredev repo 
and move from the hudson.cfg to the new jenkins.cfg, based on 
buildout.jenkins:

https://github.com/plone/buildout.jenkins

Here is the new Jenkins job configuration for buildout.coredev 4.2:

https://github.com/tisto/buildout.coredev/blob/4.2/jenkins.cfg

What do you think?

Cheers,
timo

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam