Remove self-hosted bioconda/docker backup from GitHub Actions#626
Merged
Conversation
The nightly 'Bioconda and docker backups' job ran node index.js on the github-ci self-hosted runner to push bioconda/docker to AWS/S3. We are no longer pushing to that S3 bucket, and a hung run (stuck on CLOSE-WAIT sockets to the local registry:5000) had been holding sync.lock for 2.5 days, failing every scheduled run. Take the backup out of GitHub Actions; if still wanted it should be re-homed as a cron on a VM, not on Actions. This also frees the self-hosted runner for deregistration + github-ci decommissioning.
|
❌ BioContainers CI failed for Errors (must fix):
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deletes
.github/workflows/conda.yml— the schedulednode index.js --backup --aws --condajob on theself-hostedrunner.Why
CLOSE-WAITsockets to the localregistry:5000) and heldsync.lock, so every nightly run failed with "Process is already running".Follow-ups (not in this PR)
sync.lockongithub-ci.biocontainers-ci-ebiself-hosted runner, then decommissiongithub-ci.The schedule is already disabled (
gh workflow disable) so nothing fires in the meantime.