We're updating the issue view to help you get more done. 

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

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

Status

Assignee

S. Ali Tokmen

Reporter

S. Ali Tokmen

Components

Fix versions

Priority

Major