continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luc Willems (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1572) Release should support Build Environments (formerly called Continuum Profiles)
Date Tue, 07 Oct 2008 12:22:08 GMT


Luc Willems commented on CONTINUUM-1572:

- initial  "prepare" failure was caused by a minor issues in my test so build failed because
of this 
- My "normal" build defenitions had the -Dmaven.test.skip=1 option but the release:prepare
step not (which is normal )
- once i noticed this problem and i got my working copy back OK (al version = xxx-snapshot),
i retried to see if rollback could solve this problem.
  just to check that i can go back to a valid state after a prepare error
- this is the point where i got the ClassCastException exception and rollback failed ;-(
- manually put the working copy back into good state
- run de prepare step with extra -Dmaven.test.skip=1 parameter -> OK
- run the release step with extra -Dmaven.test.skip=1 parameter -> OK

so i have 1 successfull release done :-)
still feels a little bit fragile , many things can go wrong ,even if your builds are OK
rollback doesn't seems to fix the problem always ;-(


> Release should support Build Environments (formerly called Continuum Profiles)
> ------------------------------------------------------------------------------
>                 Key: CONTINUUM-1572
>                 URL:
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Core - Profiles, Release
>    Affects Versions: 1.1-beta-4, 1.1
>            Reporter: Lóránt Pintér
>            Assignee: Maria Catherine Tan
>             Fix For: 1.2.1
> Currently there's no way to specify parameters for the release, like JVM version or MAVEN_OPTS.
I had a hard time "configuring" Maven to have enough memory during the release (actually I
had to add MAVEN_OPTS=-Xmx512m as an environment variable -- not a really nice solution).
> It would be nice to have a similar build configuration for the release as we have for
other builds, with profiles and all. Maybe a default schedule called RELEASE would do.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message