Thanks for your help Karl, but I don't think were are talking about the sam problem here. Let me try to refrase:
The problem is not wheter 355 is gren or not, the problem is that it influenced on the stable build 354. Last friday build #354 was green and stabel, along with the upstream project #79, all tests were ok, the build was finnished. We deployed the artifacts. Everything worked. (I do not have a screen shot of this) When I arrived this morning (monday), the already deployed build #354 along with upstream projekt #79 have turned red. The green build we've deployed is no longer a valid build. How is it possible that a build that has already finnished as green, later changes status to red? Why does not build #355 has its own row in the "Build History", but rather incorporated in #354? -- View this message in context: http://jenkins.361315.n4.nabble.com/New-build-brakes-already-existing-green-build-tp4403629p4404185.html Sent from the Jenkins users mailing list archive at Nabble.com.
