plone/jenkins.plone.org — Issue #1: Trigger the coredev builds when changes are pushed to packages
Author: esteele
Created: 2011-12-03 15:52:06+00:00
State: open

Pulled from our readme...

* Plone coredev is currently triggered on each github commit to the core repo
no matter to which branch. This leads to load problems on jenkins.plone.org.
As far as I understood the discussion on that topic the best way to
accomplish this is a small piece of component that sits in between github
and jenkins and can decide which commit should trigger a build. Another
option might be a Jenkins plugin. Any thoughts/ideas?

- https://github.com/conversation/github-jenkins-bridge
- http://stackoverflow.com/questions/5784329/how-can-i-make-jenkins-ci-with-git-trigger-on-pushes-to-master

=> UPDATE: If we disable the "Cross Site Request Forgery" setting in the
Jenkins configuration, the GitHub post-commit hook works.

=> UPDATE: A user "github" has been created in the Plone LDAP and granted
the right to build a job on jenkins.plone.org. See
https://github.com/plone/plone.app.discussion/admin/hooks
for an example of a post-commit hook configuration. Anonymous users are
not allowed to trigger a build.