Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
-
Platform: All, OS: All
Description
(pasted from message
http://www.nabble.com/Problem-with-incremental-builds-td24799079.html )
We're making use of the new incremental build feature, and I've noticed a problem.
Let's say I have two modules, "library" and "app", with "app" depending on
"library". If a commit fails a unit test in "library", Hudson correctly flags
the build. However, if a subsequent commit occurs on "app" (and "app" only),
Hudson will only execute the build of "app", and despite no one having committed
code to fix the unit test, Hudson reports this subsequent build as "passed".
This is because Hudson only built "app", and did not run library's unit tests.
In my opinion, if a previous build has failed, Hudson should keep using this
build's maven's "pl" argument, appending to it as necessary as more commits are
made. So, in my example, the first build would be invoked "mvn -pl library"
(since that's the module that has changed). The second build would be invoked
"-ol library, app", which is "pl of last build + new changes.
Attachments
Issue Links
- is duplicated by
-
JENKINS-4243 invalid status when maven incremental build is used
-
- Closed
-
- is related to
-
JENKINS-5121 Deploy all built modules on success, including from previous failed builds
-
- Resolved
-
Ok, this definitely won't make it in until 1.322 at the earliest - I've got a
bunch of actual paid work to do, and I'm having trouble getting my test
SCM-with-changelog working for the ITs for this feature. But I'll keep plugging
away.