Uploaded image for project: 'Codehaus Cargo'
  1. CARGO-1032

A deployment failure should produce an error rather than an info

    Details

    • Type: Improvement
    • Status: Closed (View workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects versions: 1.1.2
    • Fix versions: 1.1.3
    • Components: Maven2/Maven3
    • Labels:
      None
    • Environment:

      Hudson CI and Maven Standalone

      Description

      If the cargo maven plugin is used to deploy an application for integration test (ex. into a glassfish container) and the deployment fails the plugin just produces an info like this:

      [INFO] [talledLocalContainer] Deprecated syntax, instead use:
      [INFO] [talledLocalContainer] asadmin --interactive=false --port 4849 --user admin -passwordfile /opt/glassfishv3/.hudson/jobs/XAM Test.Setup.Application/workspace/target/cargo/configurations/glassfish3x/password.properties deploy [options] ...
      [WARNING] [talledLocalContainer] remote failure: Error occurred during deployment: Application with name de.rwth.swc.xam.tests.ear-0.0.1-SNAPSHOT is already registered. Either specify that redeployment must be forced, or redeploy the application. Or if this is a new deployment, pick a different name. Please see server.log for more details.
      [INFO] [talledLocalContainer] Command deploy failed.
      

      The problem is, that this results in the build being sucessfull and therefore triggering other builds who may rely on successful deployment.

      Also see: http://stackoverflow.com/questions/7160797/

        Attachments

          Activity

            People

            • Assignee:
              savasalitokmen Savas Ali Tokmen (Inactive)
              Reporter:
              matthiasvianden Matthias Vianden (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: