I have bb pipeline caching enabled. At the build end I see,
Build teardown1m 31s
Cache "maven": Compressing
Cache "maven": Compressed
Cache "maven": Compressed size is larger than upload limit (1 GB more than the 1 GB limit). Skipping cache upload.
Is there anyway I can use the 1 GB to provide some benefit. If I could blacklist certain jars that would help.
Could I run a script at the run of the build to delete part of ~/.m2/repository?
I added this script to the pipelines configuration. At the end of the build with deletes the artifacts generated by the build which reduced the M2 repo directory to < 1GB.
#!/usr/bin/env bash # mvn -B help:evaluate -Dexpression=settings.localRepository du -sh /root/.m2/repository/* echo du -sh /root/.m2/repository/com/* echo du -sh /root/.m2/repository/org/* echo echo "Total size:" du -sh /root/.m2/repository/ # 1.5G /root/.m2/repository/com/inferess echo "Deleting from /root/.m2/repository/com/inferess" rm -rf /root/.m2/repository/com/inferess echo echo "Total size:" du -sh /root/.m2/repository/ ## 130M /root/.m2/repository/org/apache #echo "Deleting from /root/.m2/repository/org/apache" #rm -rf /root/.m2/repository/org/apache #echo #echo "Total size:" #du -sh /root/.m2/repository/
The commented out code allowed me to identify candidates for deletion.
It would be useful to have an option to Maven caching to list paths under the repo to exclude from the cached repo. I will never need to cache artifacts the build will create.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot