I don't understand why you set 2 build definitions for the same schedule. It will be more logic to
delete the second (compile) because it's included in package phase.
As you have 2 build definitions on the same schedule, continuum run them separatly. In your case it
run compile definition first, and when it try to run package definition, scm update return no
changes, so continuum doesn't do the build.
Emmanuel
Alex Boisvert a écrit :
Hi,
I'm using continuum 1.0.2 and I've defined two goals for a Maven2 project:
Build Definitions
Goals Arguments POM File Profile Schedule From
package --batch-mode pom.xml DEFAULT DEFAULT_SCHEDULE Project Edit
<http://release.intalio.com:9999/continuum/servlet/continuum/target/BuildDefinition.vm/view/BuildDefinition/buildDefinitionId/11/id/11>
| Delete
<http://release.intalio.com:9999/continuum/servlet/continuum/target/DeleteBuildDefinition.vm/buildDefinitionId/11/id/11/executorId/maven2>
compile --batch-mode pom.xml DEFAULT
DEFAULT_SCHEDULE Project Edit
<http://release.intalio.com:9999/continuum/servlet/continuum/target/BuildDefinition.vm/view/BuildDefinition/buildDefinitionId/51/id/11>
| Delete
<http://release.intalio.com:9999/continuum/servlet/continuum/target/DeleteBuildDefinition.vm/buildDefinitionId/51/id/11/executorId/maven2>
I've discovered today that only the second goal (compile) gets run every
hour (DEFAULT_SCHEDULE). The first goal (package; which is flagged as
default) only executes if I trigger the build manually.
Is this normal?
alex
