Trigger the coredev builds when changes are pushed to packages #1

Closed
esteele opened this Issue Dec 3, 2011 · 2 comments

Projects

None yet

2 participants

@esteele
Member
esteele commented Dec 3, 2011

Pulled from our readme...

@esteele
Member
esteele commented Dec 3, 2011

The more I think about it, the more I like the idea of having a Jenkins job for each of our core packages.

If we had some sort of script/job/service that could check the sources.cfg of our coredev builds (PLIPs, other packages?), Jenkins could fire of only those buildouts that matter.

The 1 job/package setup would also allow me to check things like the changelog for proper formatting. It'd make my life easier at release time. Theoretically, we could release packages from Jenkins at some point to, but that's of low priority at the moment.

@esteele
Member
esteele commented Dec 3, 2011

Or, we automate the creation of jobs, run at regular intervals, to create one job per package per branch. On creation, the job would be tied into the proper coredev job.

Script runs... plone.app.layout has 2.1 and master branches. It creates job plone.app.layout-2.1 with post-build triggers for plone_41 and job plone.app.layout-master with post-build triggers for plone_42.

@tisto tisto closed this Jul 10, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment