Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to create a shallow clone in gitPublishReset #57

Closed
marcphilipp opened this issue Sep 29, 2018 · 6 comments
Closed

Add an option to create a shallow clone in gitPublishReset #57

marcphilipp opened this issue Sep 29, 2018 · 6 comments

Comments

@marcphilipp
Copy link

marcphilipp commented Sep 29, 2018

We use your excellent plugins to publish documentation and Javadoc to GH Pages in the junit5 repo. As you can see in this build scan, gitPublishReset takes most of the time of this build that was executed by a Travis job.

screen shot 2018-09-29 at 18 23 38

For our purposes a shallow clone of the single gh-pages branch would be sufficent to publish to our branch. This is probably not true for every project, but a configuration option that triggers the use of the grgit/JGit equivalent of --single-branch --depth=1 would really speed up our build.

@marcphilipp
Copy link
Author

Looks like it isn't possible with JGit at the moment... ajoberstar/grgit#155

@shevek
Copy link

shevek commented Mar 5, 2019

Similarly an option to clone using a local reference repository for the bulk of the data transfer might help?

@ajoberstar
Copy link
Owner

@shevek See #1 for the local repo idea. Seems like it could help a lot for bigger projects that already have that data cloned.

@liza-mae
Copy link

Any update on whether this will be supported?

ajoberstar added a commit that referenced this issue Apr 22, 2023
Uses the new property in grgit to allow shallow fetch.

Fixes #57
@marcphilipp
Copy link
Author

@ajoberstar Thanks for this! In JUnit's build, gitPublishReset went down from 3m 38s to 1m 13s. 🎉

marcphilipp added a commit to junit-team/junit5 that referenced this issue Apr 28, 2023
@ajoberstar
Copy link
Owner

Thanks to @AfzalivE for sending the original PR adding support to grgit!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants