Consider setting DOCKER_MAX_PROCS for Drone #382
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#382
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We see a lot of build failures because of collisions between simultaneous Drone builds, especially because of the
docker system prune
step in our recipe CI. Example: #369Setting the maximum number of simultaenous builds using DOCKER_MAX_PROCS could prevent this problem, at the cost of maybe slightly slower builds, if parallelism was gaining us any speed. Thoughts?
Can we pass some sort of
--filter
magic tostack-ssh-deploy
to limit the prune?