Skip to content

Commit 1d856bc

Browse files
committed
fix: refine artifact download patterns and allow failure for specific build versions in CI
1 parent c151122 commit 1d856bc

2 files changed

Lines changed: 16 additions & 0 deletions

File tree

.github/workflows/build.yml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,10 +127,19 @@ jobs: {
127127
},
128128
},
129129
{
130+
# Without a pattern, download-artifact@v4 pulls everything in
131+
# the run — including the `*.dockerbuild` metadata artifacts
132+
# that docker/build-push-action@v6 auto-uploads per build
133+
# (20 of them at matrix fan-out). Those aren't release
134+
# payloads, and one flaky download in that set will fail the
135+
# entire step after 5 retries, blocking the release. Filter
136+
# to our own tarballs; ncipollo/release-action below only
137+
# globs `artifacts/*/*.tar.gz` anyway.
130138
"name": "Download release tar files",
131139
"uses": "actions/download-artifact@v4",
132140
"with": {
133141
"path": "artifacts/",
142+
"pattern": "release-*.tar.gz",
134143
},
135144
},
136145
{ "name": "Set env TAG_NAME",

.gitlab-ci.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,13 @@ upload:
130130
paths: ["*-result.txt"]
131131
tags: [shell]
132132
rules:
133+
# Mirror the build job's allow_failure for 3.15 cells. The build stage
134+
# tolerates 3.15 failures (pip 26 / locate_file); without the matching
135+
# rule here, a failed build cell propagates a missing tarball into this
136+
# matrix cell, the curl --upload-file fails, and the whole pipeline
137+
# goes red even though build was intentionally allowed to fail.
138+
- if: '$CI_COMMIT_TAG == null && $version =~ /^3\.15/'
139+
allow_failure: true
133140
- if: $CI_COMMIT_TAG == null
134141

135142
generate_release_note:

0 commit comments

Comments
 (0)