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

Make cargo:start stop the container if startup / deployment of deployables fail

    Details

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

      Description

      See: https://groups.google.com/forum/#!topic/codehaus-cargo/vxGgWa9KPLk

      Currently if any deployable fails to be deployed during defined timeout period, Cargo throws exception causing build to fail. If maven build is running with configuration to fail at end or fail never then whole build will become inconsistent as container with failed deployable is still running while maven starts to process another module.

      It has been decided to:

      • Modify cargo:start in a way that is startup fails, the container is automatically stopped
      • Modify cargo:run so that it logs errors if starting the container fails

        Attachments

          Activity

            People

            • Assignee:
              alitokmen S. Ali Tokmen
              Reporter:
              alitokmen S. Ali Tokmen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: