Maven 2.x and 3.x Site Plugin

Allow cleaning of the remote area or staging site

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: site:deploy, site:stage(-deploy)
  • Labels:
    None
  • Number of attachments :
    0

Description

When files have been removed, they are not removed from the remote deploy area or the staging site. A new goal to clean the staging or the final deploy area would be a nice addon to this plugin.

Issue Links

is duplicated by

New Feature - A new feature of the product, which has yet to be developed. MSITE-407 feature request: "site:clean" goal

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. WAGON-343 wagon-scp should remove target area prior to uploading/unzipping new content

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.
supercedes

Improvement - An improvement or enhancement to an existing feature or task. MSITE-30 site:deploy incompatibilities with m1.02

  • 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
Anthony Whitford added a comment -

My use case is that I deploy the site files to a file share: \\server\sites
The sites are organized by project and version: \\server\sites\project\version

The CI server will build the site, let's say for 1.0-SNAPSHOT: \\server\sites\project\1.0-SNAPSHOT
Then, I will release this project, and I get a site for 1.0: \\server\sites\project\1.0

My issue is that I am getting toxic waste buildup by not removing the old 1.0-SNAPSHOT directory.
If I had a site:clean goal, I could build it into my release workflow.
Better yet, the release plugin could leverage it and automatically purge the old snapshot files.

Show
Anthony Whitford added a comment - My use case is that I deploy the site files to a file share: \\server\sites The sites are organized by project and version: \\server\sites\project\version The CI server will build the site, let's say for 1.0-SNAPSHOT : \\server\sites\project\1.0-SNAPSHOT Then, I will release this project, and I get a site for 1.0 : \\server\sites\project\1.0 My issue is that I am getting toxic waste buildup by not removing the old 1.0-SNAPSHOT directory. If I had a site:clean goal, I could build it into my release workflow. Better yet, the release plugin could leverage it and automatically purge the old snapshot files.
Hide
Permalink
Gordon McNair added a comment -

Our use case is exactly the same as Anthony's. Getting the site plugin to clean up the remote site directory to prevent having to manually manage the remote disk usage would be a huge benefit for us.

Show
Gordon McNair added a comment - Our use case is exactly the same as Anthony's. Getting the site plugin to clean up the remote site directory to prevent having to manually manage the remote disk usage would be a huge benefit for us.

People

  • Assignee:
    Unassigned
    Reporter:
    Wim Deblauwe
Vote (19)
Watch (17)

Dates

  • Created:
    Updated: