From 58181659933b8aec2f3b90faba397a8059552333 Mon Sep 17 00:00:00 2001 From: Yasset Perez-Riverol Date: Tue, 7 Jul 2026 16:17:19 +0100 Subject: [PATCH] ci: remove the self-hosted bioconda/docker backup workflow 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. --- .github/workflows/conda.yml | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 .github/workflows/conda.yml diff --git a/.github/workflows/conda.yml b/.github/workflows/conda.yml deleted file mode 100644 index 8c6187ec4..000000000 --- a/.github/workflows/conda.yml +++ /dev/null @@ -1,19 +0,0 @@ -# Calls biocontainer-ci repo / bioconda-backup script -# on self hosted node - -name: Bioconda and docker backups - -on: - schedule: - - cron: "0 23 * * * " - -jobs: - - build: - timeout-minutes: 4320 - runs-on: self-hosted - steps: - - name: Backup bioconda and docker containers to local and aws registries - run: | - cd /home/debian/sync && node index.js --backup --aws --conda --updated - cd /home/debian/sync && node index.js --docker --aws --updated