-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
Running latest Jenkins as a service on Windows.
Project sources are from git (bitbucket) repository.
Builds that pass after a failed build are reported as Fixed. My team works on different branches - this simple comparison of last build and current build is simply wrong unless you only use one branch.
Perhaps it works for some. But I'd at least appreciate being able to turn off the feature and just have every build pass or fail without any comparison to previous history.
It would be neat if it could check the history of the previous build on the same branch. But honestly, this feature just isn't really worth it. But I don't like the false flag of Fixed as 9 times out of 10 it isn't fixed, it's just a different source base.
This behaviour has, to my knowledge, always existed in Jenkins. So perhaps Bug is harsh, and Improvement might be more appropriate.