[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-08-02 Thread andrejs.sit...@gmail.com (JIRA)














































Andrejs Šitals
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















Shannon Kerr, good job on isolating this. I'm also waiting for a fix, but I didn't know how to reproduce the problem (tried with string parameters, but they worked fine).

As for workarounds, I think BUILD_NUMBER could be passed to a downstream job as a parameter by using "Predefined parameters" in "Trigger parameterized build on other projects" step - that should solve the problem with merged downstream jobs.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-07-03 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(03/Jul/13 4:13 PM)




Description:


(ChangedtoBlockerasthisbugispreventingusfromrollingoutJenkinstoproductionrightnow,but
I
couldcompletelychangeourimplementationandreducethistoCriticalorMajorIsuppose,butthatwouldbequiteabitofwork)I
startaparameterizedbuildfromprojectAviathebuildbutton.Asecondparameterizedbuildfromthesameprojectwasthenstartedviathebuildbutton,butwithdifferentparametervalues.Insteadofhavingtwojobsinthequeue,thesecondjobisnotaddedandinsteadtakesoverthefirstjobinthequeue.Ifthejobswerestartedbydifferentusers,bothusersnamesshowupastheStartedbyusers.Onlythesecondusersparametersareusedandretained.Thefirstusersjobisjustlost.Imgoingtoseeifthiseverworked,butImprettysureitdid.ImstillprettynewtoJenkins,butIthoughtIhadtestedthisoutbeforeandhadseentwoinstancesofthesamejobsittinginthequeue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-07-01 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(01/Jul/13 1:03 PM)




Priority:


Blocker
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-06-28 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:08 PM)




Component/s:


parameterized-trigger





Component/s:


parameters



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-06-28 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















I just attempted to start multiple instance of the same build, all with unique parameters and it was a mess.

Here is what I see:

1. Sometimes it created a new unique job
2. Sometimes it "merged" with the next job in the queue, replacing the parameters

In my testing I used the following parameters:

1. Branch (drop down list box of the available branches)
2. Build type (choice between -D and -R)
3. Check box for Test build (is this a test build?)

I tried different combinations of each of these and could not get consistent behavior.

We're just getting ready to roll out Jenkins and this kind of bug is really throwing off the plan to roll out.  Hope to see it fixed soon, or someone can educate me on what I'm not doing right.

Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-06-28 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:44 PM)




Priority:


Major
Blocker





Description:


(ChangedtoBlockerasthisbugispreventingusfromrollingoutJenkinstoproductionrightnow,but
I
couldcompletelychangeourimplementationandreducethistoCriticalorMajorIsuppose,butthatwouldbequiteabitofwork)I
startaparameterizedbuildfromprojectAviathebuildbutton.Asecondparameterizedbuildfromthesameprojectwasthenstartedviathebuildbutton,butwithdifferentparametervalues.Insteadofhavingtwojobsinthequeue,thesecondjobisnotaddedandinsteadtakesoverthefirstjobinthequeue.Ifthejobswerestartedbydifferentusers,bothusersnamesshowupastheStartedbyusers.Onlythesecondusersparametersareusedandretained.Thefirstusersjobisjustlost.Imgoingtoseeifthiseverworked,butImprettysureitdid.ImstillprettynewtoJenkins,butIthoughtIhadtestedthisoutbeforeandhadseentwoinstancesofthesamejobsittinginthequeue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-06-28 Thread shannonck...@gmail.com (JIRA)















































Shannon Kerr
 assigned  JENKINS-18534 to huybrechts



Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:50 PM)




Assignee:


huybrechts



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-06-28 Thread shannonck...@gmail.com (JIRA)














































Shannon Kerr
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















OK, I think I've isolated the root of this issue.  It appears that the plugin is not honoring unique values for "List Subversion Tags" type parameter.  So, if the only parameter value that is different between two build executions is the Tag or Branch selected by the user, Jenkins will combine the two and user the branch or tag selected by the second build request.

To help my team get around this for now, I've added a new parameter requesting the user type in their name.  This will keep Jim from clobbering Suzy etc.  It won't keep Jim from clobbering Jim's other branch build though.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.