You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org> on 2005/11/04 16:59:07 UTC
[jira] Updated: (CONTINUUM-34) Keep trying till build works, notify via email what is required
[ http://jira.codehaus.org/browse/CONTINUUM-34?page=all ]
Emmanuel Venisse updated CONTINUUM-34:
--------------------------------------
Description:
I don't know if this is relevant to continuum's style of building, but....
I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build.
The idea:
Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again.
Example scenario 1:
$ cvs update -dP
$ maven
....
BUILD FAILED
$ maven clean default
....
BUILD SUCCESSFUL
(email sent suggesting people do a 'maven clean default' after updating)
Example scenario 2:
$ cvs update -dP
$ maven
....
BUILD FAILED
$ maven clean default
....
BUILD FAILED
$ cvs co alanparsons
$ cd alanparsons
$ maven
....
BUILD SUCCESSFUL
(email sent suggesting people get a clean checkout of the alanparsons project before attempting to build)
was:
I don't know if this is relevant to continuum's style of building, but....
I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build.
The idea:
Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again.
Example scenario 1:
$ cvs update -dP
$ maven
....
BUILD FAILED
$ maven clean default
....
BUILD SUCCESSFUL
(email sent suggesting people do a 'maven clean default' after updating)
Example scenario 2:
$ cvs update -dP
$ maven
....
BUILD FAILED
$ maven clean default
....
BUILD FAILED
$ cvs co alanparsons
$ cd alanparsons
$ maven
....
BUILD SUCCESSFUL
(email sent suggesting people get a clean checkout of the alanparsons project before attempting to build)
Fix Version: (was: 1.0.1)
1.1
Environment:
> Keep trying till build works, notify via email what is required
> ---------------------------------------------------------------
>
> Key: CONTINUUM-34
> URL: http://jira.codehaus.org/browse/CONTINUUM-34
> Project: Continuum
> Type: Wish
> Reporter: David Blevins
> Priority: Minor
> Fix For: 1.1
>
>
> I don't know if this is relevant to continuum's style of building, but....
> I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build.
> The idea:
> Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again.
> Example scenario 1:
> $ cvs update -dP
> $ maven
> ....
> BUILD FAILED
>
> $ maven clean default
> ....
> BUILD SUCCESSFUL
> (email sent suggesting people do a 'maven clean default' after updating)
> Example scenario 2:
> $ cvs update -dP
> $ maven
> ....
> BUILD FAILED
>
> $ maven clean default
> ....
> BUILD FAILED
> $ cvs co alanparsons
> $ cd alanparsons
> $ maven
> ....
> BUILD SUCCESSFUL
> (email sent suggesting people get a clean checkout of the alanparsons project before attempting to build)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira