Skip to content

Conversation

@bbasata
Copy link
Contributor

@bbasata bbasata commented Mar 7, 2025

The next step in testing Registry manifest upload.

Ultimately, we want a pre-promotion workflow for promote-production. That workflow is in an internal repo as a pre-promotion workflow. It will upload the manifest to the staging Releases site -- not production.

For testing within a safety net, this PR configures a post-promotion workflow for promote-staging, because promote-staging is responsible for promoting artifacts to the the staging artifacts repo.

@bbasata bbasata requested a review from a team as a code owner March 7, 2025 17:43
austinvalle
austinvalle previously approved these changes Mar 7, 2025
Copy link
Member

@austinvalle austinvalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@bbasata
Copy link
Contributor Author

bbasata commented Mar 7, 2025

Pausing for a moment to 💭 through this. This will not work as written.

     // Download Registry manifest from Artifactory staging repo
     // and upload to staging Releases bucket

At pre-promotion time for promote-staging, artifacts are not yet in the staging repo.

Right now, the value is in safely exercising the upload workflow, so I think it's fine to do move this from pre- to post-promotion to get that feedback. We're in the safety net 😃 I would not do that for promote-production at all.

@bbasata bbasata changed the title Add a pre-promotion workflow to promote-staging Add a post-promotion workflow to promote-staging Mar 10, 2025
bbasata added 3 commits March 10, 2025 14:00
... because upload currently expects to download artifacts from the
staging repo.
@rainkwan rainkwan force-pushed the pre-promotion-workflow branch from cd3535f to e23c3b3 Compare March 10, 2025 18:00
@bbasata bbasata enabled auto-merge (squash) March 10, 2025 18:11
@bbasata bbasata merged commit 702cc54 into main Mar 10, 2025
68 checks passed
@bbasata bbasata deleted the pre-promotion-workflow branch March 10, 2025 18:38
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants