The version of jenkins is: 2.46.1 <http://jenkins-ci.org/>
Gerrit trigger: 2.23.1

Sorry for the description. Here are some screenshots attached.
The project is parameterized: parameter.jpg
The gerrit trigger: trigger.jpg
gerrit project provided in Plain text and i know it works because it does 
trigger but as I mentioned in the initial query it is not for every 
patchset. I do see  all the patchsets when I try querying from jenkins for 
the same project and branch. 
I have a pipeline script which I get from some other SCM location and not 
the repo I want to monitor for all the incoming patchset (new as well as 
revised)

Sorry I didnt realize about the subject line. Will take more care posting 
next time.

Thanks,
Sagar 

On Wednesday, April 26, 2017 at 1:17:36 AM UTC-7, [email protected] 
wrote:
>
> I’ve not seen this problem; our Gerrit triggers are working ok for new 
> patchsets. What version of Jenkins, Gerrit trigger, and Gerrit, are you 
> using?
>
> Your description of you configuration is a bit hard to understand, maybe 
> you could send a screenshot of the full Gerrit configuration from the job?
>
>  
>
> By the way, because there are so many Jenkins plugins, next time you might 
> want to include the word “Gerrit” in the subject line. I nearly missed this 
> message because when I glanced quickly at the subject line, I didn’t 
> realize at firs that it was something we used.
>
>  
>
> *From:* [email protected] <javascript:> [mailto:
> [email protected] <javascript:>] *On Behalf Of *Sagar Bhowmik
> *Sent:* 25 April 2017 19:17
> *To:* Jenkins Users <[email protected] <javascript:>>
> *Subject:* How to trigger job when a new patchset is uploaded for an 
> existing change
>
>  
>
> My job works well when the patchset is uploaded for first time. After that 
> when a new patchset is again uploaded on the same gerrit change, it does 
> not trigger again. I already tried the Trigger On Comment Added Contains 
> Regular Expression. I have these Trigger On currently in the same job. 
>
> Patchset Create
>
> Comment Added Contains Regular Expression
>
>  
>
> -- 
>
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not 
> use, copy, retain, distribute or disclose the information in or attached to 
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and 
> not necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England 
> and Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/92272939-32e0-4f75-9d2c-21a38d01e98e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to