[build-helper] Consider changing default phase for remove-project-artifact mojo

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[build-helper] Consider changing default phase for remove-project-artifact mojo

Stevo Slavic
Hello Codehaus mojo community,

build-helper-maven-plugin has a nice goal, remove-project-artifact, which I find useful to cleanup large project artifacts, to minimize project disk space footprint on CI server.

By default this plugin goal binds to package phase, but as it's supposed to execute before plugin's typically bound to package phase, like maven-jar-plugin, I'd propose to change default phase from package to prepare-package - to free up disk space before new package gets made.

I'm interested what does community and plugin developers think about this idea?

Kind regards,
Stevo Slavic.
Reply | Threaded
Open this post in threaded view
|

Re: [build-helper] Consider changing default phase for remove-project-artifact mojo

Baptiste MATHUS-4
Hi,

Well, it depends. But I think there's two aspects here:
* cleaning the local repository: for me, it's important to just wipe it out on a regular basis (between once a day and once a week for example). Then, dedicate a local repository/cache *per job*. (Side note: disk space is cheap, far cheaper than spending engineer hours to glean some GB of disk space or resolve build concurrency issues).
* cleaning the target directory: If you're using Jenkins, we do that cleanup using a jenkins plugin : "workspace cleanup plugin".
We simply delete any "**/target" directory in the job workspace. We gained a lot of disk space *on a average basis" (I mean, it's only interesting when you have a fair amount of jobs and those jobs are not always built very often).

-- Baptiste


2013/7/11 Stevo Slavić <[hidden email]>
Hello Codehaus mojo community,

build-helper-maven-plugin has a nice goal, remove-project-artifact, which I find useful to cleanup large project artifacts, to minimize project disk space footprint on CI server.

By default this plugin goal binds to package phase, but as it's supposed to execute before plugin's typically bound to package phase, like maven-jar-plugin, I'd propose to change default phase from package to prepare-package - to free up disk space before new package gets made.

I'm interested what does community and plugin developers think about this idea?

Kind regards,
Stevo Slavic.

--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor ! nbsp;!