-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Hudson version 1.353
Two unrelated modules A and B. According to the parent pom, B is built after A (but does not depend on it).
1. John makes a commit to module A that breaks it.
2. Hudson forks a build that compiles module A and fails.
3. Paul makes a commit to module B that breaks it also.
4. Hudson forks a build that intends to compile module B, but first compiles module A (it is still failed) and fails.
5. John fixes module A.
6. Hudson forks a build that compiles A only (B is not among its dependencies).
==> Build is marked successful while there is a "hidden time-bomb" in module B.
- duplicates
-
-
- Resolved
-
[JENKINS-6976] In incremental build mode - if a breaking commit is done to a module while another module is broken, the build eventually succeeds
victor_bronstein
created issue -
| Component/s | New: maven2 [ 15487 ] | |
| Component/s | Original: infrastructure [ 15687 ] |
kutzi
made changes -
| Link |
New:
This issue duplicates |
kutzi
made changes -
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Jenkins IRC Bot
made changes -
| Component/s | New: maven-plugin [ 16033 ] | |
| Component/s | Original: maven2 [ 15487 ] |
| Workflow | Original: JNJira [ 137073 ] | New: JNJira + In-Review [ 187360 ] |