Continuum look at scm changes, if it contains some sources updates, it build
the project.
Then, it looks at dependencies list, if a dependency (that is a continuum
project too) is updated (new build result in success), continuum build the
project
With no SCM changes and no dependencies, if the build definition is marked as
"always build" and the build isn't forced, continuum won't build the project.
Emmanuel
Damien Lecan a écrit :
Hum, I'm working with Continuum 1.1-beta-3
Damien
2007/9/24, Damien Lecan <[EMAIL PROTECTED]>:
Hello,
I would like to understand how Continuum knows which sub-projects of a
multi-module project have to be built.
All sub-projects are in eparate projects under a main project group.
it seems that build of a project is done when :
- sources are updated
- dependency projects have been "updated" (= built or sources updated ?)
- ...
I would like to know all the rules in order to understand why some
projects are built whereas I can read for theses projects :
SCM Changes : No SCM changes
Dependencies Changes : No dependencies changes
Thanks
Damien Lecan
