-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
Ubuntu 8
Job Priority stopped working when updating Jenkins to LTS v1.532.1.
Also, I have version 1.3 of PrioritySorter installed (now it goes at 2.4) and it doesn't shows up the option to update to the latest version of the plugin.
I have also uninstalled, deleted PrioritySorter data (old data), restarted Jenkins and installed again, and it only lets install version 1.3.
[JENKINS-21236] PrioritySorter Plugin 1.3 and Jenkins v1.532.1 Problem
pedro reis
created issue -
| Assignee | Original: bklarson [ bklarson ] | New: Magnus Sandberg [ emsa23 ] |
Now the update center for lts contains 2.4 so you should be able to install it.
Please let me know if everything works for you if you encounter any issues.
pedro reis
added a comment - Hi Magnus,
"stopped working" doesn't mean it shows erros, it simply isn't prioritizing anything anymore at v1.532.1.
I wasn't planning using 1.532.1 yet, but the recommended
wget http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war
has downloaded this version, so I have trusted this!
Ok, now at update center I can see 2.4, thanks. I'll give it a try.
pedro reis
added a comment - Hi Magnus,
"stopped working" doesn't mean it shows erros, it simply isn't prioritizing anything anymore at v1.532.1.
I wasn't planning using 1.532.1 yet, but the recommended
wget http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war
has downloaded this version, so I have trusted this!
Ok, now at update center I can see 2.4, thanks. I'll give it a try. pedro reis
added a comment - There must be some problem, because it doesn't upgrades to 2.4. pedro reis
added a comment - ok, it upgraded now. (this time, I have updated some other plugins along with priority sorter, and it did the trick)
will report if now works.
pedro reis
added a comment - ok, it upgraded now. (this time, I have updated some other plugins along with priority sorter, and it did the trick)
will report if now works. pedro reis
added a comment - Nope,
It still doesn't work on 2.4 @ 1.532.1!
Priority order not respected when asking the jobs to start simultaneously:
2014-01-07 14:54:05.907000
2014-01-07 14:54:05.908000
2014-01-07 14:54:05.908000
2014-01-07 14:54:05.909000
2014-01-07 14:54:05.910000
2014-01-07 14:54:05.911000
Also the jobs were on build queue and started to build without respecting the priority order.
pedro reis
added a comment - Nope,
It still doesn't work on 2.4 @ 1.532.1!
Priority order not respected when asking the jobs to start simultaneously:
2014-01-07 14:54:05.907000
2014-01-07 14:54:05.908000
2014-01-07 14:54:05.908000
2014-01-07 14:54:05.909000
2014-01-07 14:54:05.910000
2014-01-07 14:54:05.911000
Also the jobs were on build queue and started to build without respecting the priority order. The sorting doesn't happen immediately when a jobs are added, it just happens at intervals (this is how Jenkins works and is nothing that is controlled by the plugin) this means that jobs might get started when added if there's room for them.
If the slaves are all busy you should see the queue getting sorted, I have not tested with 1.531.1 but I have not seen any issues like this in any other version I have tested.
If you look under "Troubleshooting" on the wiki page it describes how to turn on some extra logging to verify what priorities gets assigned to jobs, you can also see when Jobs jumps between states in the queue and when they get removed fro the queue (started).
Could you please turn on this logging and provide logs in this issue that showcases the bad behaviour, this will give me a better starting point to find out what is going on.
pedro reis
added a comment - Does the new version of priority plugin only allow priority between 1 and 5?
I need at least a 1 to 10! (Old version was 1 to 100...)
pedro reis
added a comment - Does the new version of priority plugin only allow priority between 1 and 5?
I need at least a 1 to 10! (Old version was 1 to 100...)
What do you mean with "stopped working" do you get any errors?
The update center for LTS is, as far as I can see, not updated - I would not recommend using 1.532.1 until it is officially announced on the web-site.