Almost every weekend we get the same error in Jenkins (1.414) as follows: 1. Friday, a build as made, every test is ok and the build is green. You can download the artifacts and everything works fine
2. When returning on monday, we find that our last build that was green on friday has now turned red. A new build has been triggered during the weekend (by who knows what, no additional checkins were made). Instead of logging this as a new build Jenkins append it to the existing green build and in the end failing them both to red. See the screen shots, build #354 was green when it was finished this friday. Why doesn't build 355 has its own row in the build history? How can a build first finnish as green and then switch status some days later? In screen shot 2 you can see that both 354 and 355 are connected to the same upstream project build #79. The project build #79 was completly finished on friday, how can this new build 355 (that was started on sunday) be connected to a already finnished build? http://jenkins.361315.n4.nabble.com/file/n4403629/jenkins1.jpg http://jenkins.361315.n4.nabble.com/file/n4403629/jenkins2.jpg -- View this message in context: http://jenkins.361315.n4.nabble.com/New-build-brakes-already-existing-green-build-tp4403629p4403629.html Sent from the Jenkins issues mailing list archive at Nabble.com.
