Continuum

Can not add more than one build tool to a Build Environment

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.3.4 (Beta)
  • Fix Version/s: None
  • Component/s: Web interface
  • Environment:
    Replicated on: Solaris Sparc, Mac OSX
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

The web interface no longer allows an admin user to add more than one "Installation" to a Build Environment.

Steps to Replicate:
Install 1.3.4 Beta...start Continuum
Add two installations (I added the ANT tool, and the Maven2 Tool)
Left Nav: Build Environment
Click on Add Button
Type a name for the build env. I called it "Test"
Click on Save Button
Combo Box has my Installation selected...click on Add
Switch Combo box to another instalation (I switched to ant). click on Add

Expected Result:
-> A second installation is bound to the build environment

Observed Result:
-> The initial installation seems to be overwritten by the second.

See attached screenshot.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

I can reproduce this on trunk.

If this configuration is stored in continuum.xml, an easy workaround would be to edit the file directly. If (as I suspect) it's stored in the database, it will be harder to make changes outside of the app to work around this bug.

Show
Wendy Smoak added a comment - I can reproduce this on trunk. If this configuration is stored in continuum.xml, an easy workaround would be to edit the file directly. If (as I suspect) it's stored in the database, it will be harder to make changes outside of the app to work around this bug.
Hide
Permalink
Wendy Smoak added a comment -

Actually... this is working as designed, but the documentation needs to be clarified:

On http://continuum.apache.org/docs/1.3.4/administrator_guides/buildEnvironment.html under "Attach JDK..." it says:

"In the modification mode of a build environment, adding an already attached type will override the existing one."

This actually applies to all types, not just JDK.

You can only have one JDK in a Build Environment, and (apparently!) you can only have one Build Tool (Maven or Ant) in a Build Environment.

Show
Wendy Smoak added a comment - Actually... this is working as designed, but the documentation needs to be clarified: On http://continuum.apache.org/docs/1.3.4/administrator_guides/buildEnvironment.html under "Attach JDK..." it says: "In the modification mode of a build environment, adding an already attached type will override the existing one." This actually applies to all types, not just JDK. You can only have one JDK in a Build Environment, and (apparently!) you can only have one Build Tool (Maven or Ant) in a Build Environment.
Hide
Permalink
Wendy Smoak added a comment -

Editing the subject to better describe what you reported. You can add more than one installation, just not more than one of the same type of installation.

What is the use case you have for needing more than one build tool in a single build environment?

Show
Wendy Smoak added a comment - Editing the subject to better describe what you reported. You can add more than one installation, just not more than one of the same type of installation. What is the use case you have for needing more than one build tool in a single build environment?
Hide
Permalink
Brian Holland added a comment -

Wendy -

Thank you for the clarification. Yes, after examining the functionality further, the design constraint you mentioned does seem to be working as designed. I was trying to add both a maven and ant tool installation to an individual build environment b/c of some automation projects we have built. We have an ant build.xml file that performs some work, after which it "exec's" maven explicitly to finish the work. For this reason, I was wanting to define both the ant and maven installation.

We have found some alternative ways to ensure our approach works, so either:
A) The current design constraint (can't have ant and maven builder as part of a single installation) is valid, and this ticket should be closed.

B) The current design constraint is artificial, and thus could be relaxed...which would mean this ticket really becomes a feature enhancement.

With the tight integration between ant and maven, I would be interested to know if option B is possible.

Show
Brian Holland added a comment - Wendy - Thank you for the clarification. Yes, after examining the functionality further, the design constraint you mentioned does seem to be working as designed. I was trying to add both a maven and ant tool installation to an individual build environment b/c of some automation projects we have built. We have an ant build.xml file that performs some work, after which it "exec's" maven explicitly to finish the work. For this reason, I was wanting to define both the ant and maven installation. We have found some alternative ways to ensure our approach works, so either: A) The current design constraint (can't have ant and maven builder as part of a single installation) is valid, and this ticket should be closed. B) The current design constraint is artificial, and thus could be relaxed...which would mean this ticket really becomes a feature enhancement. With the tight integration between ant and maven, I would be interested to know if option B is possible.

People

  • Assignee:
    Unassigned
    Reporter:
    Brian Holland
Vote (0)
Watch (2)

Dates

  • Created:
    Updated: