Add nightly release pipeline validation#28176
Add nightly release pipeline validation#28176ashley-cui wants to merge 2 commits intocontainers:mainfrom
Conversation
Our new release has been mostly stable at this point, remove legacy actions. Signed-off-by: Ashley Cui <acui@redhat.com>
Build installers nightly, and test that our bot key is still valid. This is to catch hiccups before release time. The intention is that after this is tested, the build-artifacts can be used in release.yml, like it is used in the validation action But for now, the actual release does not use the build-artifacts action yet, let's let the testing bake a little first. Signed-off-by: Ashley Cui <acui@redhat.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| version_display: ${{ steps.set-version.outputs.version_display }} | ||
| steps: | ||
| - name: Checkout Version | ||
| uses: actions/checkout@v6 |
Check failure
Code scanning / zizmor
unpinned action reference Error
| id: set-version | ||
| run: | | ||
| sha=$(git rev-parse --short HEAD) | ||
| if [[ "${{ inputs.version }}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+ ]]; then |
Check failure
Code scanning / zizmor
code injection via template expansion Error
| run: | | ||
| sha=$(git rev-parse --short HEAD) | ||
| if [[ "${{ inputs.version }}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+ ]]; then | ||
| echo "version_display=${{ inputs.version }}" >> "$GITHUB_OUTPUT" |
Check failure
Code scanning / zizmor
code injection via template expansion Error
| if [[ "${{ inputs.version }}" =~ ^v[0-9]+\.[0-9]+\.[0-9]+ ]]; then | ||
| echo "version_display=${{ inputs.version }}" >> "$GITHUB_OUTPUT" | ||
| else | ||
| echo "version_display=${{ inputs.version }}-$sha" >> "$GITHUB_OUTPUT" |
Check failure
Code scanning / zizmor
code injection via template expansion Error
| echo "version_display=${{ inputs.version }}-$sha" >> "$GITHUB_OUTPUT" | ||
| fi | ||
| - name: Set up Go | ||
| uses: actions/setup-go@v6 |
Check failure
Code scanning / zizmor
unpinned action reference Error
|
|
||
| build-artifacts-latest-branch: | ||
| name: Build Artifacts (latest release branch) | ||
| uses: ./.github/workflows/build-artifacts.yml |
Check warning
Code scanning / zizmor
secrets unconditionally inherited by called workflow Warning
|
|
||
| build-artifacts-single: | ||
| name: Build Artifacts | ||
| uses: ./.github/workflows/build-artifacts.yml |
Check warning
Code scanning / zizmor
secrets unconditionally inherited by called workflow Warning
| **Workflow run:** $RUN_URL | ||
|
|
||
| **Failed jobs:** | ||
| - validate-tokens: ${{ needs.validate-tokens.result }} |
Check notice
Code scanning / zizmor
code injection via template expansion Note
|
|
||
| **Failed jobs:** | ||
| - validate-tokens: ${{ needs.validate-tokens.result }} | ||
| - build-artifacts-main: ${{ needs.build-artifacts-main.result }} |
Check notice
Code scanning / zizmor
code injection via template expansion Note
| **Failed jobs:** | ||
| - validate-tokens: ${{ needs.validate-tokens.result }} | ||
| - build-artifacts-main: ${{ needs.build-artifacts-main.result }} | ||
| - build-artifacts-latest-branch: ${{ needs.build-artifacts-latest-branch.result }} |
Check notice
Code scanning / zizmor
code injection via template expansion Note
|
A friendly reminder that this PR had no activity for 30 days. |
2 participants
Build installers nightly, and test that our bot key is still valid. This is to catch hiccups before release time.
The intention is that after this is tested, the build-artifacts can be used in release.yml, like it is used in the validation action
But for now, the actual release does not use the build-artifacts action yet, let's let the testing bake a little first.
Checklist
Ensure you have completed the following checklist for your pull request to be reviewed:
commits. (
git commit -s). (If needed, usegit commit -s --amend). The author email must matchthe sign-off email address. See CONTRIBUTING.md
for more information.
Fixes: #00000in commit message (if applicable)make validatepr(format/lint checks)Noneif no user-facing changes)Does this PR introduce a user-facing change?