![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
bklarson
|
|
Components:
|
prioritysorter |
|
Created:
|
20/Mar/14 8:53 AM
|
|
Description:
|
We switched our quite large Jenkins installation (~4000 jobs) now after running in legacy mode for some time. The initial save took about an hour to update all configurations and it was successfull. At least the jobs now showed the new 5 default priority values and the priorities where honoured.
After restarting Jenkins priority sorter is back to legacy mode and what I think makes this bug critical: all jobs now share the same default priority of 100.:-/
|
|
Environment:
|
Jenkins 1.555 and all plugins latest, priority sorter is 2.6
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Dirk Kuypers
|
|
|
|
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.
