|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
This issue was originally reported as issue
JENKINS-7785.When running a job on a Jenkins slave that deploys a maven site, the slave will automatically archive all site artifacts to the Jenkins master. In other words, the site artifacts are transported both to the maven repo (Nexus in our case), and the Jenkins master.
In our scenario, the size of the site artifacts is approx. 5GB. We'd like to finish this deploy job as fast as possible, so therefore we like to have the possibility to disable the site artifact archiving to the master.
I have a patch ready in my local clone of the maven-plugin repository, implementing a new option "Disable automatic site documentation artifact archiving". I'll submit a pull request later today.