You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "apupier (via GitHub)" <gi...@apache.org> on 2026/07/08 09:11:06 UTC
[PR] Use git shallow clone of depth 1 for Jenkins deploy job [camel-quarkus]
apupier opened a new pull request, #8843:
URL: https://github.com/apache/camel-quarkus/pull/8843
it allows to reduce the amount of space taken by the .git folder. it will decrease the size of it from 350M to 18M. Given that it is kept in workspace history of the last 6 builds, it will save 2.28G of disk space on Jenkins.
it also saves few seconds to do the git clone.
Not doing it for the Sonarcloud job as it requires the git history
<!-- Uncomment and fill this section if your PR is not trivial
[ ] An issue should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by #.
[ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough.
[ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close the named issue upon merging the pull request. Using them is typically a good idea.
[ ] Please run mvn process-resources -Pformat (and amend the changes if necessary) before sending the pull request.
[ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Use git shallow clone of depth 1 for Jenkins deploy job [camel-quarkus]
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier commented on PR #8843:
URL: https://github.com/apache/camel-quarkus/pull/8843#issuecomment-4913251547
Note that I'm wondering if we could not even completely delete the workspace after the build as it is used only for Sonarcloud and snapshot deploy, I do not think that we have really needs to be able to investigate to the workspace after the build.
Even if not storing the workspace, this would gain few seconds and 330M on disk space
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Use git shallow clone of depth 1 for Jenkins deploy job [camel-quarkus]
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier merged PR #8843:
URL: https://github.com/apache/camel-quarkus/pull/8843
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org