Skip to content

Release from staging #91

Release from staging

Release from staging #91

Manually triggered August 10, 2024 02:24
Status Failure
Total duration 20m 53s
Artifacts

staging-release.yaml

on: workflow_dispatch
Check staging release matches
7s
Check staging release matches
Get package matrix
24s
Get package matrix
Matrix: staging-release-images
Matrix: Update Windows and macOS packages
S3 - update source bucket
58s
S3 - update source bucket
Matrix: Release Windows images
Matrix: S3 - update APT packages bucket
Matrix: S3 - update YUM packages bucket
Sign container image manifests
44s
Sign container image manifests
Run container smoke tests
2m 11s
Run container smoke tests
Matrix: staging-release-images-arch-specific-legacy-tags
Matrix: Release latest Linux container images
Get Windows checksums for new release
7s
Get Windows checksums for new release
Create the Github Release once packages and containers are up
5s
Create the Github Release once packages and containers are up
Update top-level bucket info
5s
Update top-level bucket info
Run package smoke tests
2m 31s
Run package smoke tests
Upload Cosign public key for verification
0s
Upload Cosign public key for verification
Create docs updates for new release
10s
Create docs updates for new release
Create version update PR for new release
14s
Create version update PR for new release
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
edsiper
approved Aug 10, 2024
release
edsiper
approved Aug 10, 2024
release and
edsiper
approved Aug 10, 2024
edsiper
approved Aug 10, 2024
release
edsiper
approved Aug 10, 2024
edsiper
approved Aug 10, 2024
release

Annotations

1 error and 1 warning
Sign container image manifests
Process completed with exit code 1.
Get package matrix
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/