Sorry was too fast ...
On 21/07/18 20:59, Karl Heinz Marbaise wrote:
Hi to you Tamaya Devs..
currently I'm investigating what the projects can do to reduce the
number of disk space issues...
After I've taken a look into your build configuration I've found some
things which might be improved:
1. "clean install deploy --U -fae"
1.1 "-P coverage clean install deploy"
usage in
https://builds.apache.org/view/S-Z/view/Tamaya/job/Tamaya-Branch-Master-with-Coverage/configure
If you do an install and "deploy" this means that the install life cycle
phase is duplicated and will be executed twice..which takes some time...
So I would suggest to simplify this to:
"clean deploy -fae -U"
2. In the Build configuration you haven't configured to use "Use private
Maven repository"
This means in consequence that all artifacts which are
downloaded/created via the build are stored into the home directory
($HOME/.m2/repository) of the node on which this builds run..(or more
accurate the home directory of the user under which Jenkins is running)..
I would suggest to turn that on and select via the drop down list "Local
to workspace" which results in a directory inside your workspace
".repository" which contains all the artifacts.
3. Log Rotation
The number of builds is limited. very good.
Unfortunately the configuration "Max # of builds to keep
with artifacts" via "Advanced" Button is not configured.
The question is: Do you really need to archive the artifacts
which have been created and deployed into remote repository
also on Jenkins ?
I have checked the following configurations:
https://builds.apache.org/job/Tamaya-Sandbox-Master/configure
https://builds.apache.org/view/S-Z/view/Tamaya/job/Tamaya-Master-branch/configure
https://builds.apache.org/view/S-Z/view/Tamaya/job/Tamaya-Branch-Master-with-Coverage/configure
Kind regards
Karl Heinz Marbaise
WDYT ?
Kind regards
Karl Heinz Marbaise
Apache Maven PMC
