Repository navigation
chore: authenticate the GitHub API calls in the integration workflow - #290
Merged
Merged
Conversation
New master 20250410
Increase artifact retention time a little
newMaster_20261020: merge devel into master * commit '5d9e685': fix: skip integration tests on the central DIRACGrid repository fix: allow merge commits in the commit message check fix: purge site environment variables before repopulating installEnv fix: Increase artifact retention time a little fix: Make genericOptions a list
fstagni
force-pushed
the
ci/authenticate-api-calls
branch
from
November 9, 2026 17:15
e8a2668 to
c254cce
Compare
The four calls listing the DIRAC releases were unauthenticated and therefore rate limited per IP; on shared runner IPs they intermittently return an error body, leaving the DIRAC release version empty and failing the job. Use 'gh api' with the workflow token instead (same treatment as DIRACGrid/DIRAC#8879 for the Pilot artifacts listing).
fstagni
force-pushed
the
ci/authenticate-api-calls
branch
from
November 9, 2026 18:39
c254cce to
014bc71
Compare
aldbr
approved these changes
Nov 10, 2026
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
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.
CI fix: authenticate the GitHub API calls in the integration workflow
The four calls listing the DIRAC releases in
.github/workflows/integration.yml:version=$(curl -s "https://api.github.com/repos/DIRACGrid/DIRAC/releases" | jq -r '.[].tag_name' | ...)are unauthenticated and therefore rate limited to 60 requests/hour per IP — and runner IPs are shared. When throttled, the response body has no
.tag_nameto extract,versioncomes out empty, and sourcing/cvmfs/dirac.egi.eu/dirac/${version}/...fails: intermittent job failures unrelated to the PR content.Per review, the four calls now use `gh api repos/DIRACGrid/DIRAC/releases --jq '.[].tag_name'` with `GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}` in each step's env (same treatment as DIRACGrid/DIRAC#8879, where the review suggested `gh`). Public endpoint, the token only lifts the rate limit.
Evidence
129226434925:jq: Cannot iterate over nullfrom an unauthenticated artifacts listing) and fixed there by chore: authenticate the artifacts API call in the PilotWrapper workflow DIRAC#8879.python -c yaml.safe_loadpasses; the diff is one header added to 4 identical lines.Merge Danger
Door: two-way — adds an auth header to public API calls; at worst the same flakiness as today.
Blast Radius: CI only.