Cargo

Easy way to clean deployments of a container

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 1.5.0
  • Component/s: Maven2
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

It would be helpful, if an existing running container could be cleaned from previously (failed) deployments.

E.g. by adding a new "deployer-clean" goal, which clears the "deployment"-folder of a container.

Issue Links

depends upon

Task - A task that needs to be done. CARGO-427 Add a new API to verify if a Deployable is deployed

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is related to

New Feature - A new feature of the product, which has yet to be developed. CARGO-242 cargo:smartdeploy

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Savas Ali Tokmen added a comment -

And does the existing cargo:undeploy satisfy this requirement? If not, why?

Show
Savas Ali Tokmen added a comment - And does the existing cargo:undeploy satisfy this requirement? If not, why?
Hide
Permalink
Lars Fischer added a comment -

I understand that cargo:undeploy removes the known/configured deployables for a given project.

But sometimes, there is some garbage or other deployments from older project runs left inside the containers deployment folder. It would be nice if this could be cleaned using a simple maven cargo call.

Show
Lars Fischer added a comment - I understand that cargo:undeploy removes the known/configured deployables for a given project. But sometimes, there is some garbage or other deployments from older project runs left inside the containers deployment folder. It would be nice if this could be cleaned using a simple maven cargo call.
Hide
Permalink
Savas Ali Tokmen added a comment -

OK, I see.

The trouble here is that most deployers are not aware of all the things that are deployed.

Do you want to have this for local or remote deployer?

Show
Savas Ali Tokmen added a comment - OK, I see. The trouble here is that most deployers are not aware of all the things that are deployed. Do you want to have this for local or remote deployer?
Hide
Permalink
Lars Fischer added a comment -

I see the difficulties for remote deployers, that they can only access identifiable deployables.

A local deployer could clean everything inside the "deploy" folder. Maybe using optional includes/excludes.

Show
Lars Fischer added a comment - I see the difficulties for remote deployers, that they can only access identifiable deployables. A local deployer could clean everything inside the "deploy" folder. Maybe using optional includes/excludes.
Hide
Permalink
Savas Ali Tokmen added a comment -

Well, in JBoss for example the JBoss services (such as the web service) are also deployed (and configured) via the "deploy" folder. In JOnAS, database definitions are also in deploy.

So, this could actually mess up "a lot" of stuff :o

Oc course, if you have a magic idea it is always welcome

Show
Savas Ali Tokmen added a comment - Well, in JBoss for example the JBoss services (such as the web service) are also deployed (and configured) via the "deploy" folder. In JOnAS, database definitions are also in deploy. So, this could actually mess up "a lot" of stuff :o Oc course, if you have a magic idea it is always welcome

People

  • Assignee:
    Unassigned
    Reporter:
    Lars Fischer
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: