-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.46.3
PrioritySorter-plugin 2.5.1
While with JENKINS-44014 no exception is thrown anymore, nothing is being done with the started job as well, only a warning is printed. However, after restart of Jenkins, the ItemCache is always empty, so any job that was in the queue at the time of the restart will trigger this.
So instead, if itemInfo cannot be found, a new ItemInfo from the LeftItem should be created, priority applied, and added with onNewItem(); then it should proceed with that.
Am I right?