-
Notifications
You must be signed in to change notification settings - Fork 46
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
Workers occupied by larger repos #2411
Comments
We are cloning the repo there only to get the config, right? Then making a shallow clone makes complete sense, I just don't think passing There is also another option, treeless clone:
That's about 39 MiB in total and it could in theory work in place of full clones. |
A config option with a default to clone just the last commit might be a good approach. |
That's actually not true, we are getting the config via API earlier. The cloning happens anytime |
With this change, for copr builds also try to not clone the repo. Related to packit#2411
With this change, for copr builds also try to not clone the repo. Related to packit#2411
With this change, for copr builds also try to not clone the repo. Related to packit#2411
Utilise LocalProjectBuilder for LP initalisation With this change, for copr builds also try to not clone the repo. Fixes #1955 Related to #2411 For now no release notes, I would like to see whether this will work on staging as intended. RELEASE NOTES BEGIN N/A RELEASE NOTES END Reviewed-by: František Lachman <[email protected]>
Description
During the problems with our queue on Monday, it's been discovered that the last executed command in both of our
long-running
workers has been (or replace with different repository):Given the size of the systemd repository from the example and its presence in both of the workers, it is suspected that the clone of the large repository resulted in the queue being “choked” by cloning large repository in the workers.
Since this has been caught as part of the
run_copr_build_handler
, we do not need the full history, it will be cloned for the build (and potential user-specified actions) in Copr build environment anyways.TODO
--depth=1
sync-release
anduptream-koji-build
Sizes of repository
Current command »218 MiB«
Only cloning the latest commit »16 MiB«
The text was updated successfully, but these errors were encountered: