Re: Plone 4.2 Experimental Jenkins job

On Tuesday, April 10, 2012 at 2:39 PM, Timo Stollenwerk wrote:
> Hi Eric,
> 
> I just wanted to give you a short update on the new (experimental) 
> Jenkins job for Plone 4.2. Here is a list of the jobs that I created so far:
> 
> 
> Plone 4.2
> ---------
> 
> https://jenkins.plone.org/job/plone-4.2/
> 
> This job checks out buildout.coredev and fetches all packages that are 
> currently under development. The naginator plugin re-runs the job in 
> case a github checkout fails. This works quite well so far.
> 
> All coredev packages on github have a post-commit trigger that trigger 
> this job. The script that sets those triggers after reading the sources 
> of buildout.coredev also worked quite well and we might want to include 
> it into the coredev buildout to make sure the triggers are always set up 
> for all coredev packages.
> 
> 
> Plone 4.2 - Tests
> -----------------
> 
> https://jenkins.plone.org/job/plone-4.2-tests/
> 
> Shares the workspace with the Plone 4.2 job and runs alltests if the 
> first job was successful. This job also sends email notifications. The 
> problem here is that we don't get the git commit messages that actually 
> triggered the build (e.g. https://jenkins.plone.org/job/plone-4.2/70/). 
> I'm not sure about the best solution for that problem yet. We either 
> have to use the Jenkins github plugin which will provide us with the 
> commit messages (but that would mean we would have to checkout all 
> packages which would slow down the job), or find another way to get 
> these messages into Jenkins. If you have an idea how to solve this let 
> me know.
> 
> 
> Plone 4.2 - Test Coverage / Code Analysis
> -----------------------------------------
> 
> https://jenkins.plone.org/job/plone-4.2-test-coverage
> https://jenkins.plone.org/job/plone-4.2-code-analysis
> 
> These jobs are not fully configured yet. The buildout sections are ready 
> though. I think we can't run test coverage and code analysis on each 
> commit since these jobs just take too long right now. I would suggest 
> that we run them on a nightly basis on the latest successful test 
> job/artifact.
> 
> 
> Shall we replace the old Plone_4.2 test jobs now or do you prefer to 
> wait until I finished the full setup (github commit messages / test 
> coverage / code analysis)?
> 
> Cheers,
> timo
> 
> 

 
Fantastic work, Timo. It's an obvious improvement over the ones we currently have. I'm all in favor of switching to these now. We'll work out the commit messages as we go.

As a side note for everyone, we're now officially supporting both Python 2.6 and 2.7. I'd like to run against both, if we could. Are we better off with two separate jobs or as a single multi-configuration one?

Eric

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam