I am having intermittent issues with Jenkins where the dashboard will indicate that a job has never been run even though it has.
The files and folders from the previous build(s) are all in place and, if I run the build again, it usually updates the status correctly after the build completes. However, that status may go back to indicating that the job has never been built at a later time.
Most of the time it is not the latest job/build which loses its status. The status may switch to the correct data after a different job is built, but not always.
I have yet to determine any kind of pattern as to which builds are being ignored, much less why.
Has anyone else seen this behavior?
Update: I am running Jenkins 1.497 on Windows Server 2008 R2.
The issue has supposedly been fixed with Jenkins version 1.505. (Fix put in for version 1.502 was apparently insufficient)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With