Thx Aaron, I didn't know it. I will study this approach too.
Cheers Arnaud On Thu, Mar 29, 2012 at 2:31 AM, Aaron Walker <[email protected]>wrote: > Arnaud, > > Another solution is to use the the github-sqs-plugin > https://wiki.jenkins-ci.org/display/JENKINS/GitHub+SQS+Plugin this has > the advantage of not requiring Jenkins to be accessible via the Internet. > > Currently the plugin automatically creates the Amazon SQS queue but right > now need to manually the Sqs github hook. I'm working on being able to > automatically add this hook. > > Also I'm waiting on this pull request > https://github.com/github/github-services/pull/270 to fix the payload > encoding but once this is done it's all good to go.... > > The only downside is you need a Amazon AWS account. The volumes of > messages you'd generate the SQS Free tier would be more than enough > > Just another option for you to consider :) > > > Aaron Walker > > On 28/03/2012, at 8:43 PM, Arnaud Héritier wrote: > > Thinking more : > > Do you thing that it could be possible in the github plugin to do like > in the git plugin and to have a unique and not protected URL to configure > github hooks. > Could we reuse the same one as the git plugin but with the ability to > manage POST requests ? > > 2012/3/28 Arnaud Héritier <[email protected]> > >> Hi, >> >> I'm trying to setup git hooks to trigger jobs after a push. >> Our repositories are hosted on GitHub >> I found that there was 2 similar solutions : >> * One with the Git plugin : >> https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository >> * One with the GitHub plugin : >> https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin#GithubPlugin-TriggerabuildwhenachangeispushedtoGitHub >> >> The Git version has the advantage to have a uniq not protected URL but >> works with a GET query and requires that the job configures a polling >> trigger >> The GitHub version has the advantage to be able to automatically >> configure the hook on GitHub side but it requires to have a technical >> account on jenkins side to access to protected jobs and it works with POST >> (due to GitHub) >> >> Couldn't we try to improve our user experience by trying to merge such >> solutions and to propose something more generic ? >> >> Any ideas ? >> >> -- >> ----- >> Arnaud Héritier >> 06-89-76-64-24 >> http://aheritier.net >> Mail/GTalk: [email protected] >> Twitter/Skype : aheritier >> >> > > > -- > ----- > Arnaud Héritier > 06-89-76-64-24 > http://aheritier.net > Mail/GTalk: [email protected] > Twitter/Skype : aheritier > > > -- ----- Arnaud Héritier 06-89-76-64-24 http://aheritier.net Mail/GTalk: [email protected] Twitter/Skype : aheritier
