search

mohamicorp / stash-jenkins-postreceive-webhook

Webhook used to notify Jenkins when commits are made to Stash
Other
138 stars 98 forks source link

Configuration check triggered every single job in our jenkins environment #140

Open gabriellezbautista opened 9 years ago

gabriellezbautista commented 9 years ago

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

ashnazg commented 9 years ago

Every job in your jenkins instance, or every job tied to the one repository whose configuration you were testing?

gabriellezbautista commented 9 years ago

Every job in the jenkins instance.

Gabrielle Rafael Z. Bautista Technology Delivery Center (TDC) GSCMT Mailboxmailto:m25622@att.com | 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 [notifications@github.com] 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.

ashnazg commented 9 years ago

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".

mikesir87 commented 9 years ago

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?

gabriellezbautista commented 9 years ago

I will ask the Jenkins admin (I am the Stash admin) :)

diakula commented 8 years ago

We get something similar:

Since upgrade we get all jobs triggering on commit. Jenkins ver. 1.596.1 Atlassian Bitbucket v4.1.3

phardakerffdc commented 8 years ago

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.