continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-2612) Release Perform should allow selection of environment for final build
Date Fri, 08 Apr 2011 04:02:22 GMT


Brett Porter commented on CONTINUUM-2612:

I'm unclear what you mean - it is possible to select the environment on the release build.

If you want to do this across multiple environments, you can repeat it by entering the tag
URL instead of performing the already completed release again.

> Release Perform should allow selection of environment for final build
> ---------------------------------------------------------------------
>                 Key: CONTINUUM-2612
>                 URL:
>             Project: Continuum
>          Issue Type: Improvement
>          Components: Release
>    Affects Versions: 1.3.6
>         Environment: RedHat, Oracle 1.6 JDK, IBM J9 1.6 JDK, IBM J9 1.5 JDK
>            Reporter: Daun DeFrance
> We perform three different builds using three jdks configured as environments within
continuum.  We also use Maven profiles to specify classifiers for those builds.  For example,
our artifacts look like:
> [artifact]-WAS7.ear (built with IBM J9 1.6 JDK)
> [artifact]-JBOSS.ear (built with Oracles 1.6 JDK)
> When we to a prepare release, we are allowed to specify environment.  The prepare relese
creates the tag, etc.  However, in our situation, we only want one tag per release number,
but we want to generate three released builds off that one tag.  The code is not changed per
environment, so one tag is sufficient.
> When we perform a release, we cannot specify an environment (and corresponding Maven
profile for the classifier), so we cannot specify a different environment for the release.
> I would like the ability to tag once and generate three different environmental releases
builds, each one compiled against a different JDK.
> We are not using distributed builds at this time.

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