You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like the plugin should generate the repository within the workspace. As an administrator, it's hard for me to track down which maven job is generating so much disk space depending on the size of the yum repository. I was just lucky that I was able to track down the job that re-downloaded 10's of GB worth of data by re-downloading the entire yum repository.
The text was updated successfully, but these errors were encountered:
Trying to be more specific. It seems like if you don't set -Ds3repo.stagingDirectory, it sets up a temp directory outside of your project root directory. In this particular case, it created a random directory in /tmp. Instead it should create a directory within the project root directory.
I feel like the plugin should generate the repository within the workspace. As an administrator, it's hard for me to track down which maven job is generating so much disk space depending on the size of the yum repository. I was just lucky that I was able to track down the job that re-downloaded 10's of GB worth of data by re-downloading the entire yum repository.
The text was updated successfully, but these errors were encountered: