Details
-
Bug
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
1.1-beta-2, 1.1-beta-3
-
None
-
None
Description
Based on this discussion
http://www.nabble.com/When-builds-are-done-in-multi-module-projects---tf4508232.html
Continuum doesn't handle correctly previous build results when several build definitions are enabled for the same project group.
As Emmanuel said :
After to check scm changes, Continuum look at dependencies changes. To do that, it look only at dependencies that are continuum project too. For them, a new version is detected if the latest build result of the dependency/project is more recent than the latest build result of the current build definition. In case on more than one build def, we can't know if all build def of the dependency generate an artifact or not, we know only if a new build was done and we add it in dependencies changes.
Attachments
Issue Links
- is related to
-
CONTINUUM-1724 Queue build definitions separately
-
- Open
-
- relates to
-
CONTINUUM-686 Provide each build definition for a given project with its own checked-out workspace.
-
- Open
-
-
CONTINUUM-509 Ability to process scheduled builds the same as forced builds.
-
- Open
-
-
CONTINUUM-564 Change focus of build from projects to Build Definitions
-
- Open
-