ci: push artifacts to Harbor instead of GitHub storage#26
Merged
Conversation
Replace actions/upload-artifact with pushes to the in-cluster Harbor OCI registry (registry.gerowallet.io, project gero) to stop consuming the shared org-wide GitHub Actions artifact storage quota. Both mainnet.yml and preprod.yml uploaded JaCoCo coverage exec files (coverage reports, no matching download-artifact). Each now sets up ORAS and pushes the exec via `oras push`, preserving `if: always()` and using `continue-on-error: true` so artifact upload never fails CI. Credentials come from existing repo secrets; no values hardcoded. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
compgen -G on a literal dir path with trailing slash reports a match even when the dir is absent, so tar got a nonexistent path and failed. Glob-expand then test each match with [ -e ]. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
The shared org-wide GitHub Actions artifact storage quota keeps filling up. This moves CI artifacts off GitHub storage and onto the in-cluster Harbor OCI registry (
registry.gerowallet.io, projectgero, public ingress + TLS).What changed
Both
mainnet.ymlandpreprod.ymlpreviously usedactions/upload-artifact@v4to upload a JaCoCo coverage exec (exportJacoco/jacoco-mainnet.exec/jacoco-preprod.exec) withif: always(). Neither has a matchingdownload-artifact, so both are coverage reports → routed to Harbor.Each upload step is replaced with:
Set up ORAS(oras-project/setup-oras@v2)Push ... to Harborstep that tars the exec and runsoras pushtoregistry.gerowallet.io/gero/maestro-java-client-ci:<tag>.Preserved
if: always(); push usescontinue-on-error: trueso artifact upload never fails CI. Credentials come from existing repo secrets (HARBOR_REGISTRY,HARBOR_USERNAME,HARBOR_PASSWORD) via${{ secrets.* }}— nothing hardcoded. Run commands only reference trusted env vars /${GITHUB_*}(nogithub.event.*interpolation).Harbor repo:tag
registry.gerowallet.io/gero/maestro-java-client-ci:jacoco-mainnet-<run_id>-<run_attempt>registry.gerowallet.io/gero/maestro-java-client-ci:jacoco-preprod-<run_id>-<run_attempt>Do not merge yet.
🤖 Generated with Claude Code