-
Bug
-
Resolution: Cannot Reproduce
-
Critical
We've recently noticed on our Jenkins instance (at build.kde.org) that builds which are unstable are no longer considered "Successful" by Jenkins.
This means that all of our views are now broken, because we've used "Successful" as meaning it successfully built (even if tests failed). Our expectations appear to align with the Jenkins terminology guide ( https://wiki.jenkins.io/display/JENKINS/Terminology )
This behaviour appeared sometime after Jenkins 2.184, and can be viewed at https://build.kde.org/job/Applications/view/Everything%20-%20stable-kf5-qt5/job/kopete/job/stable-kf5-qt5%20SUSEQt5.12/
(Note that only Build #1 is considered Successful, even though all builds of that job had the result of being Unstable. The correct behaviour in this instance should be for the latest Successful activity for that job to be Build #4 - as it did complete successfully, even if it is unstable)
- relates to
-
JENKINS-37862 Extract build symlink handling to a plugin
-
- Resolved
-
Over the past week we've started receiving additional complaints that a number of projects were not getting builds triggered. Examination of the Polling logs would show something like the following:
Examining the Jenkins Core changelog indicated that maintenance of symlinks within Jenkins Core for jobs/projects had been removed and transferred to a plugin. Following installation of that plugin and running jobs again, we've found that correct functionality (both in terms of the branches being polled by Jenkins and the views being updated).
As such this now appears to be a regression, and given it prevents Git polling from working properly in certain cases (when it's managed as part of a Declarative Pipeline) it actually breaks core functionality of Jenkins.