stash-jenkins-postreceive-webhook
stash-jenkins-postreceive-webhook copied to clipboard
mohamicorp
Configuration check triggered every single job in our jenkins environment
We recently upgraded Stash to 3.9.1 and upgraded Stash Jenkins hook to 2.7.0. When we did the check, it ran all the builds
Every job in your jenkins instance, or every job tied to the one repository whose configuration you were testing?
Every job in the jenkins instance.
Gabrielle Rafael Z. Bautista Technology Delivery Center (TDC) GSCMT Mailboxmailto:[email protected] | Global SCM Team Wikihttp://wiki.web.att.com/display/GSCMTeam/Global+SCM+Team | tSpace Communityhttp://tspace.web.att.com/communities/community/centralscm
Technology Delivery Transformation (TDT) Continue transformation of Software Delivery through enhanced processes and tools that improve quality, productivity and customer satisfaction
From: Chuck Burgess [[email protected]] Sent: Thursday, July 30, 2015 12:41 AM To: Nerdwin15/stash-jenkins-postreceive-webhook Cc: BAUTISTA, GABRIELLE RAFAEL Subject: Re: [stash-jenkins-postreceive-webhook] Configuration check triggered every single job in our jenkins environment (#140)
Every job in your jenkins instance, or every job tied to the one repository whose configuration you were testing?
— Reply to this email directly or view it on GitHubhttps://github.com/Nerdwin15/stash-jenkins-postreceive-webhook/issues/140#issuecomment-126012921.
I don't see how jobs configured against other repositories could be triggered by a notification from this one repository... I'd think that to be a Jenkins bug, unless its hook API is such that it does indeed accept a call in a format that means "trigger everything, without regard to target repo".
Agreed. I'm not sure how the notification could do that. Do you have any access logs to your Jenkins instance showing the URL being sent?
We get something similar:
- we have a repo with multiple Jenkins jobs.
- many depend on each other hence do not have any Poll SCM checked.
- many have periodic build set.
Since upgrade we get all jobs triggering on commit. Jenkins ver. 1.596.1 Atlassian Bitbucket v4.1.3
We are also experiencing this - we have many jobs pointing to say, a branch named "develop", only one of which has Poll SCM checked. When someone pushes to the branch, all the jobs are triggered, rather than just the job with Poll SCM enabled.
