Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2017-11-30 Thread Cyril
Hi Cosmo. Sorry for the late response, I was on vacation. Unfortunately I don’t think I can be very helpful as I don’t work in the same company anymore and I don’t remember what I did exactly even after reading all the messages again. I’m pretty sure that I did not do anything else than what is

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2017-11-22 Thread Cosmo
@Cyril -- I am having the same issue as in your original post. I don't understand your solution though. I have webhooks defined for my RepoA and RepoB. In the "Build Triggers" section of the job config I have only "Github hook trigger" -- presumably this will only trigger a build on pushes to

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-27 Thread Cyril
not? >>> >>> Enabling "Don't trigger a build on commit notifications” means the build >>> won’t trigger even if notifyCommit is received. >>> >>> >>> >>> >>> >>> From: <jenkins...@googlegroups.c

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-26 Thread Cyril
ans the build >> won’t trigger even if notifyCommit is received. >> >> >> >> >> >> From: <jenkins...@googlegroups.com> on behalf of Cyril < >> cyril@gmail.com> >> Reply-To: "jenkins...@googlegroups.com" <jenkins...@g

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-26 Thread Cyril
To: "jenkins...@googlegroups.com " < > jenkins...@googlegroups.com > > Date: Friday, September 23, 2016 at 5:43 PM > To: Jenkins Users <jenkins...@googlegroups.com > > Cc: ingunawa <ingu...@cisco.com > > Subject: Re: Jenkins builds being triggered despite ³

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-23 Thread Cyril
cyril@gmail.com > > Reply-To: "jenkins...@googlegroups.com " < > jenkins...@googlegroups.com > > Date: Friday, September 23, 2016 at 2:57 PM > To: Jenkins Users <jenkins...@googlegroups.com > > Subject: Jenkins builds being triggered despite “Don't trigger

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-23 Thread Cyril
ead. > > -Indra > > From: <jenkins...@googlegroups.com > on behalf of Cyril < > cyril@gmail.com > > Reply-To: "jenkins...@googlegroups.com " < > jenkins...@googlegroups.com > > Date: Friday, September 23, 2016 at 2:57 PM > To: Jenkins Users <je

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-23 Thread Indra Gunawan (ingunawa)
kins Users <jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>> Subject: Jenkins builds being triggered despite "Don't trigger a build on commit notifications" I have a Pipeline job that checkouts a git repository (let's call is "repoA") a

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-23 Thread Indra Gunawan (ingunawa)
sci-users@googlegroups.com>> Subject: Jenkins builds being triggered despite "Don't trigger a build on commit notifications" I have a Pipeline job that checkouts a git repository (let's call is "repoA") and passes it to some other downstream jobs for further processing. T

Re: Jenkins builds being triggered despite ³Don't trigger a build on commit notifications²

2016-09-23 Thread Indra Gunawan (ingunawa)
roups.com<mailto:jenkinsci-users@googlegroups.com>" <jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>> Date: Friday, September 23, 2016 at 2:57 PM To: Jenkins Users <jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com>&g

Jenkins builds being triggered despite “Don't trigger a build on commit notifications”

2016-09-23 Thread Cyril
I have a Pipeline job that checkouts a git repository (let's call is "repoA") and passes it to some other downstream jobs for further processing. The job's script is stored in a different git repo (let's call it "repoB"). This job is configured with the "Poll SCM" option so that any changes