![]() |
|
|
|
|
Change By:
|
Daniel Beck
(16/Jun/14 10:50 PM)
|
|
Affects Version/s:
|
current
|
|
Environment:
|
Ubuntu 12.04 Server, VMWare Fusion
|
|
Description:
|
Update:
Since this appears to be an issue with the
Different values
selected
branch, I think this is actually a bug in the
for 'List
Subversion
plugin.
====================
(rewriting the description)
When two different jobs from the same project are started by the same or different users and the only difference, besides possibly the user, is the branch/tag name, the jobs are combined in the queue and executed as a single job. This makes no sense though since user Jim could have selected branch "bugfix" and user Suzy could have selected branch "feature_1". Since Suzy was second, we end up only building "feature_1" and slapping both Jim and Suzy
Tags
'
s names on the build.
Other build
parameters
prevent the jobs from being combined in the queue, but a branch/tag selected from the SVN plugin's drop down list does
are
not
considered in determining parameter equality
.
=======================
ListSubversionTagsParameterValue needs to implement hashCode
(
original description
)
I start a parameterized build from project A via the build button.
A second parameterized build from the same project was then started via the build button, but with different parameter values.
Instead of having two jobs in the queue, the second job is not added
and
instead takes over the first job in the queue
equals() properly
.
If the jobs were started by different users, both users names show up as the "Started by" users.
Only the second user's parameters are used and retained. The first user's job is just lost.
I'm going to see if this ever worked, but I'm pretty sure it did. I'm still pretty new to Jenkins, but I thought I had tested this out before and had seen two instances of the same job sitting in the queue.
|
|
Component/s:
|
core
|
|
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/d/optout.
