You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Punkin Head <pu...@gmail.com> on 2006/02/03 15:28:47 UTC
Error in detecting changes
When Continuum does a new build, it seems to detect the CVS revision that is
equivalent to the build number. For example, one of our modules is on build
25 but CVS revision 34 and the comments for the changes on the build result
page are from CVS revision 25. Is there a way to match these so that we can
see who did what?
Thanks,
Adam
--
www.punkinshred.net // punkin'head official homepage
www.myspace.com/punkinhead <-- for true shred
Re: Error in detecting changes
Posted by Punkin Head <pu...@gmail.com>.
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,742
[Thread-1] INFO ContinuumScm - Updating project: id:
'108', name 'WRAT Parent'.
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - cvsRoot:
:pserver:[userTakenOut]@[serverTakenOut]:2401/usr/local/cvsroot/proj-103/source
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - passFile: C:\Documents and
Settings\[userTakenOut]\.cvspass
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - cvsroot
:pserver:continuum@sv102:2401/usr/local/cvsroot/proj-103/source
already exist in C:\Documents and Settings\[userTakenOut]\.cvspass. SKIPPED.
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
INFO ScmManager - Executing: cvs -f -q update -d
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
INFO ScmManager - Working directory: c:\Program
Files\Apache Software Foundation\continuum-1.0.2\working-directory\108
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - Working directory: c:\Program
Files\Apache Software Foundation\continuum-1.0.2\working-directory\108
INFO | jvm 1 | 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - Command line: cvs -f -q update -d
Filed as http://jira.codehaus.org/browse/CONTINUUM-582
On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> Strange.
>
> I wanted log of continuum.
>
> Probably a bug. File an issue, I'll at it.
>
> Emmanuel
>
> Punkin Head a écrit :
> > The pom.xml is version 1.34.
> >
> > [INFO] Scanning for projects...
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] Building WRAT Parent
> > [INFO] task-segment: [clean, deploy]
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] [clean:clean]
> > [INFO] [install:install]
> > [INFO] Installing c:\Program Files\Apache Software Foundation\continuum-
> > 1.0.2\working-directory\108\pom.xml to C:\Documents and
> >
> Settings\continuum.MOBILVOX\.m2\repository\com\mobilvox\wrat\application-parent\1.1-SNAPSHOT\application-
> > parent-1.1-SNAPSHOT.pom
> > [INFO] [deploy:deploy]
> > [INFO] Retrieving previous build number from mv-repo
> > Uploading:
> >
> file:\\dc103\software\.m2\repository/com/mobilvox/wrat/application-parent/1.1-SNAPSHOT/application-
> > parent-1.1-20060202.212006-1.pom
> > 5K uploaded
> > [INFO] Retrieving previous metadata from mv-repo
> > [INFO] Uploading repository metadata for: 'artifact
> > com.mobilvox.wrat:application-parent'
> > [INFO] Retrieving previous metadata from mv-repo
> > [INFO] Uploading repository metadata for: 'snapshot
> > com.mobilvox.wrat:application-parent:1.1-SNAPSHOT'
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] BUILD SUCCESSFUL
> > [INFO]
> >
> ----------------------------------------------------------------------------
> > [INFO] Total time: 1 second
> > [INFO] Finished at: Thu Feb 02 16:20:06 EST 2006
> > [INFO] Final Memory: 3M/6M
> > [INFO]
> >
> ----------------------------------------------------------------------------
> >
> > On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
> >
> >>Is it your pom.xml that have this version?
> >>
> >>Can you send log traces of a build execution on this project.
> >>
> >>Emmanuel
> >>
> >>Punkin Head a écrit :
> >>
> >>>The version in CVS is 1.34 (with an update by another individual) but,
> >>
> >>the
> >>
> >>>Continuum build number is 25. On CVS 1.25 I was the one who commited
> >>
> >>the
> >>
> >>>changes and it is those comments that are on the Continuum build
> changes
> >>>page, not the ones from CVS version 1.34.
> >>>
> >>>On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
> >>>
> >>>
> >>>>What do you mean? What is a CVS revision?
> >>>>
> >>>>When continuum does a new build, it run the following command 'cvs -f
> -q
> >>>>update -d'
> >>>>A build number is internal to Continuum and cvs doesn't know it.
> >>>>
> >>>>Emmanuel
> >>>>
> >>>>Punkin Head a écrit :
> >>>>
> >>>>
> >>>>>When Continuum does a new build, it seems to detect the CVS revision
> >>>>
> >>>>that is
> >>>>
> >>>>
> >>>>>equivalent to the build number. For example, one of our modules is
> on
> >>>>
> >>>>build
> >>>>
> >>>>
> >>>>>25 but CVS revision 34 and the comments for the changes on the build
> >>>>
> >>>>result
> >>>>
> >>>>
> >>>>>page are from CVS revision 25. Is there a way to match these so that
> >>
> >>we
> >>
> >>>>can
> >>>>
> >>>>
> >>>>>see who did what?
> >>>>>
> >>>>>Thanks,
> >>>>>
> >>>>>Adam
> >>>>>
> >>>>>--
> >>>>>www.punkinshred.net // punkin'head official homepage
> >>>>>
> >>>>>www.myspace.com/punkinhead <-- for true shred
> >>>>>
> >>>>
> >>>>
> >>>
> >>>--
> >>>www.punkinshred.net // punkin'head official homepage
> >>>
> >>>www.myspace.com/punkinhead <-- for true shred
> >>>
> >>
> >>
> >
> >
> > --
> > www.punkinshred.net // punkin'head official homepage
> >
> > www.myspace.com/punkinhead <-- for true shred
> >
>
>
--
www.punkinshred.net // punkin'head official homepage
www.myspace.com/punkinhead <-- for true shred
Re: Error in detecting changes
Posted by Emmanuel Venisse <em...@venisse.net>.
Strange.
I wanted log of continuum.
Probably a bug. File an issue, I'll at it.
Emmanuel
Punkin Head a écrit :
> The pom.xml is version 1.34.
>
> [INFO] Scanning for projects...
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building WRAT Parent
> [INFO] task-segment: [clean, deploy]
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] [install:install]
> [INFO] Installing c:\Program Files\Apache Software Foundation\continuum-
> 1.0.2\working-directory\108\pom.xml to C:\Documents and
> Settings\continuum.MOBILVOX\.m2\repository\com\mobilvox\wrat\application-parent\1.1-SNAPSHOT\application-
> parent-1.1-SNAPSHOT.pom
> [INFO] [deploy:deploy]
> [INFO] Retrieving previous build number from mv-repo
> Uploading:
> file:\\dc103\software\.m2\repository/com/mobilvox/wrat/application-parent/1.1-SNAPSHOT/application-
> parent-1.1-20060202.212006-1.pom
> 5K uploaded
> [INFO] Retrieving previous metadata from mv-repo
> [INFO] Uploading repository metadata for: 'artifact
> com.mobilvox.wrat:application-parent'
> [INFO] Retrieving previous metadata from mv-repo
> [INFO] Uploading repository metadata for: 'snapshot
> com.mobilvox.wrat:application-parent:1.1-SNAPSHOT'
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Feb 02 16:20:06 EST 2006
> [INFO] Final Memory: 3M/6M
> [INFO]
> ----------------------------------------------------------------------------
>
> On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
>>Is it your pom.xml that have this version?
>>
>>Can you send log traces of a build execution on this project.
>>
>>Emmanuel
>>
>>Punkin Head a écrit :
>>
>>>The version in CVS is 1.34 (with an update by another individual) but,
>>
>>the
>>
>>>Continuum build number is 25. On CVS 1.25 I was the one who commited
>>
>>the
>>
>>>changes and it is those comments that are on the Continuum build changes
>>>page, not the ones from CVS version 1.34.
>>>
>>>On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>>>
>>>
>>>>What do you mean? What is a CVS revision?
>>>>
>>>>When continuum does a new build, it run the following command 'cvs -f -q
>>>>update -d'
>>>>A build number is internal to Continuum and cvs doesn't know it.
>>>>
>>>>Emmanuel
>>>>
>>>>Punkin Head a écrit :
>>>>
>>>>
>>>>>When Continuum does a new build, it seems to detect the CVS revision
>>>>
>>>>that is
>>>>
>>>>
>>>>>equivalent to the build number. For example, one of our modules is on
>>>>
>>>>build
>>>>
>>>>
>>>>>25 but CVS revision 34 and the comments for the changes on the build
>>>>
>>>>result
>>>>
>>>>
>>>>>page are from CVS revision 25. Is there a way to match these so that
>>
>>we
>>
>>>>can
>>>>
>>>>
>>>>>see who did what?
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Adam
>>>>>
>>>>>--
>>>>>www.punkinshred.net // punkin'head official homepage
>>>>>
>>>>>www.myspace.com/punkinhead <-- for true shred
>>>>>
>>>>
>>>>
>>>
>>>--
>>>www.punkinshred.net // punkin'head official homepage
>>>
>>>www.myspace.com/punkinhead <-- for true shred
>>>
>>
>>
>
>
> --
> www.punkinshred.net // punkin'head official homepage
>
> www.myspace.com/punkinhead <-- for true shred
>
Re: Error in detecting changes
Posted by Punkin Head <pu...@gmail.com>.
The pom.xml is version 1.34.
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building WRAT Parent
[INFO] task-segment: [clean, deploy]
[INFO]
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [install:install]
[INFO] Installing c:\Program Files\Apache Software Foundation\continuum-
1.0.2\working-directory\108\pom.xml to C:\Documents and
Settings\continuum.MOBILVOX\.m2\repository\com\mobilvox\wrat\application-parent\1.1-SNAPSHOT\application-
parent-1.1-SNAPSHOT.pom
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from mv-repo
Uploading:
file:\\dc103\software\.m2\repository/com/mobilvox/wrat/application-parent/1.1-SNAPSHOT/application-
parent-1.1-20060202.212006-1.pom
5K uploaded
[INFO] Retrieving previous metadata from mv-repo
[INFO] Uploading repository metadata for: 'artifact
com.mobilvox.wrat:application-parent'
[INFO] Retrieving previous metadata from mv-repo
[INFO] Uploading repository metadata for: 'snapshot
com.mobilvox.wrat:application-parent:1.1-SNAPSHOT'
[INFO]
----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Feb 02 16:20:06 EST 2006
[INFO] Final Memory: 3M/6M
[INFO]
----------------------------------------------------------------------------
On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> Is it your pom.xml that have this version?
>
> Can you send log traces of a build execution on this project.
>
> Emmanuel
>
> Punkin Head a écrit :
> > The version in CVS is 1.34 (with an update by another individual) but,
> the
> > Continuum build number is 25. On CVS 1.25 I was the one who commited
> the
> > changes and it is those comments that are on the Continuum build changes
> > page, not the ones from CVS version 1.34.
> >
> > On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
> >
> >>What do you mean? What is a CVS revision?
> >>
> >>When continuum does a new build, it run the following command 'cvs -f -q
> >>update -d'
> >>A build number is internal to Continuum and cvs doesn't know it.
> >>
> >>Emmanuel
> >>
> >>Punkin Head a écrit :
> >>
> >>>When Continuum does a new build, it seems to detect the CVS revision
> >>
> >>that is
> >>
> >>>equivalent to the build number. For example, one of our modules is on
> >>
> >>build
> >>
> >>>25 but CVS revision 34 and the comments for the changes on the build
> >>
> >>result
> >>
> >>>page are from CVS revision 25. Is there a way to match these so that
> we
> >>
> >>can
> >>
> >>>see who did what?
> >>>
> >>>Thanks,
> >>>
> >>>Adam
> >>>
> >>>--
> >>>www.punkinshred.net // punkin'head official homepage
> >>>
> >>>www.myspace.com/punkinhead <-- for true shred
> >>>
> >>
> >>
> >
> >
> > --
> > www.punkinshred.net // punkin'head official homepage
> >
> > www.myspace.com/punkinhead <-- for true shred
> >
>
>
--
www.punkinshred.net // punkin'head official homepage
www.myspace.com/punkinhead <-- for true shred
Re: Error in detecting changes
Posted by Emmanuel Venisse <em...@venisse.net>.
Is it your pom.xml that have this version?
Can you send log traces of a build execution on this project.
Emmanuel
Punkin Head a écrit :
> The version in CVS is 1.34 (with an update by another individual) but, the
> Continuum build number is 25. On CVS 1.25 I was the one who commited the
> changes and it is those comments that are on the Continuum build changes
> page, not the ones from CVS version 1.34.
>
> On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
>>What do you mean? What is a CVS revision?
>>
>>When continuum does a new build, it run the following command 'cvs -f -q
>>update -d'
>>A build number is internal to Continuum and cvs doesn't know it.
>>
>>Emmanuel
>>
>>Punkin Head a écrit :
>>
>>>When Continuum does a new build, it seems to detect the CVS revision
>>
>>that is
>>
>>>equivalent to the build number. For example, one of our modules is on
>>
>>build
>>
>>>25 but CVS revision 34 and the comments for the changes on the build
>>
>>result
>>
>>>page are from CVS revision 25. Is there a way to match these so that we
>>
>>can
>>
>>>see who did what?
>>>
>>>Thanks,
>>>
>>>Adam
>>>
>>>--
>>>www.punkinshred.net // punkin'head official homepage
>>>
>>>www.myspace.com/punkinhead <-- for true shred
>>>
>>
>>
>
>
> --
> www.punkinshred.net // punkin'head official homepage
>
> www.myspace.com/punkinhead <-- for true shred
>
Re: Error in detecting changes
Posted by Punkin Head <pu...@gmail.com>.
The version in CVS is 1.34 (with an update by another individual) but, the
Continuum build number is 25. On CVS 1.25 I was the one who commited the
changes and it is those comments that are on the Continuum build changes
page, not the ones from CVS version 1.34.
On 2/3/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> What do you mean? What is a CVS revision?
>
> When continuum does a new build, it run the following command 'cvs -f -q
> update -d'
> A build number is internal to Continuum and cvs doesn't know it.
>
> Emmanuel
>
> Punkin Head a écrit :
> > When Continuum does a new build, it seems to detect the CVS revision
> that is
> > equivalent to the build number. For example, one of our modules is on
> build
> > 25 but CVS revision 34 and the comments for the changes on the build
> result
> > page are from CVS revision 25. Is there a way to match these so that we
> can
> > see who did what?
> >
> > Thanks,
> >
> > Adam
> >
> > --
> > www.punkinshred.net // punkin'head official homepage
> >
> > www.myspace.com/punkinhead <-- for true shred
> >
>
>
--
www.punkinshred.net // punkin'head official homepage
www.myspace.com/punkinhead <-- for true shred
Re: Error in detecting changes
Posted by Emmanuel Venisse <em...@venisse.net>.
What do you mean? What is a CVS revision?
When continuum does a new build, it run the following command 'cvs -f -q update -d'
A build number is internal to Continuum and cvs doesn't know it.
Emmanuel
Punkin Head a écrit :
> When Continuum does a new build, it seems to detect the CVS revision that is
> equivalent to the build number. For example, one of our modules is on build
> 25 but CVS revision 34 and the comments for the changes on the build result
> page are from CVS revision 25. Is there a way to match these so that we can
> see who did what?
>
> Thanks,
>
> Adam
>
> --
> www.punkinshred.net // punkin'head official homepage
>
> www.myspace.com/punkinhead <-- for true shred
>
Re: Behavior with multiple goals
Posted by Emmanuel Venisse <em...@venisse.net>.
Alex Boisvert a écrit :
> Yes, I understand the "package" goal is a superset of the "compile"; I
> mostly wanted to understand why I didn't see it happening. Thanks for
> your clarification.
>
> Are you saying that if the build definitions were set on different
> schedules the behavior would be different?
yes.
Actually, a changes check is done between two build, so if you don't have changes between two
schedules, the second won't be run. We'll fix it in 1.0.3, We'll check if projects has been modified
since the latest execution of current build definition.
>
> Let's say I have a goal "package" run every hour and a goal "release"
> run every day. Would "release" happen if it is run after "package"? Or
> should I set up two different projects for this?
"release will be run if you have changes in your scm since latest build of "package".
Emmanuel
>
> alex
>
>
>
> Emmanuel Venisse wrote:
>
>
>>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
>>>
>>>
>>
>
>
>
>
Re: Behavior with multiple goals
Posted by Alex Boisvert <bo...@intalio.com>.
Yes, I understand the "package" goal is a superset of the "compile"; I
mostly wanted to understand why I didn't see it happening. Thanks for
your clarification.
Are you saying that if the build definitions were set on different
schedules the behavior would be different?
Let's say I have a goal "package" run every hour and a goal "release"
run every day. Would "release" happen if it is run after "package"? Or
should I set up two different projects for this?
alex
Emmanuel Venisse wrote:
> 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
>>
>>
>
Re: Behavior with multiple goals
Posted by Emmanuel Venisse <em...@venisse.net>.
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
>
>
Behavior with multiple goals
Posted by Alex Boisvert <bo...@intalio.com>.
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