-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Version 1.329
Setup
Incremental build for a maven2 multi module project (module A, B and C). Target is "clean install" and "Deploy artifacts to Maven repository" is checked.
Scenario
- Modules A and B are changed of which the change in module A causes a test to fail in that module.
- The build fails as unstable after both module A and B are built, and no module is deployed even if module B built ok. Fair.
- A fix is submitted for the failing test in module A.
- The fixed module A is rebuilt including the dependant module C and all is successfull again. Ok.
- Modules A and C are deployed to the repository, but not B! Not ok!
Module B should also be deployed once the project is successfully built again. It's not ok to have to go to Hudson and manually force module B to be (re-) deployed.
This is related to JENKINS-4152 in some sense, but specific for the deploy step after the build.
- is duplicated by
-
JENKINS-5639 Missing modules in deploying to maven repository in Incremental build
- Resolved
- is related to
-
JENKINS-5764 incremental builds leave modules unbuilt upon failure
- Resolved
-
JENKINS-4152 Incremental builds should include previous builds' modules if previous build failed
- Resolved
-
JENKINS-13758 Incremental Builds: If a build is aborted right after a failed one, not all necessary modules are build
- Open