Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update BCK bucket upload to properly check for latest release and do prerelease upload #12240

Open
rtibbles opened this issue Jun 4, 2024 · 0 comments · May be fixed by #12453
Open

Update BCK bucket upload to properly check for latest release and do prerelease upload #12240

rtibbles opened this issue Jun 4, 2024 · 0 comments · May be fixed by #12453
Assignees
Labels
DEV: dev-ops Continuous integration & deployment

Comments

@rtibbles
Copy link
Member

rtibbles commented Jun 4, 2024

Observed behavior

Currently the BCK bucket upload never runs because of a check against a non-existent attribute of the release event payload.

Expected behavior

Upload prereleases to a prerelease bucket (under the secret BCK_PRERELEASE_BUILD_ARTIFACT_GCS_BUCKET) for early warnings of deployment issues.

Update the final release check following the guidelines here for determining if a release is the latest release or not: https://github.com/orgs/community/discussions/64734

For all prereleases, we should also upload hashi assets to the bucket stored at this secret: STUDIO_BCK_CONTENT_STATIC_BUCKET

@rtibbles rtibbles self-assigned this Jun 4, 2024
@rtibbles rtibbles added the DEV: dev-ops Continuous integration & deployment label Jun 4, 2024
@rtibbles rtibbles linked a pull request Jul 16, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV: dev-ops Continuous integration & deployment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant