-
Notifications
You must be signed in to change notification settings - Fork 495
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
feat(release): check for marketplace update #6426
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
tomcat323
changed the title
feat: check marketplace update in release
feat(release): check marketplace update in release
Jan 24, 2025
tomcat323
changed the title
feat(release): check marketplace update in release
feat(release): check marketplace update
Jan 24, 2025
tomcat323
changed the title
feat(release): check marketplace update
feat(release): check for marketplace update
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
reviewed
Jan 24, 2025
justinmk3
approved these changes
Jan 27, 2025
tomcat323
added a commit
that referenced
this pull request
Feb 1, 2025
## Problem in #6426, a new release pipeline stage was added that checks the marketplace extension has been updated. This PR addes a stage check and only look for an existing version of the extension when in BETA. Output in beta: <img width="1074" alt="Screenshot 2025-01-30 at 12 45 07 PM" src="https://github.com/user-attachments/assets/ee0b8df7-cd89-4e44-a99b-9746134a8aa9" /> unblocks: https://pipelines.amazon.com/pipelines/AWSVSCodeInfrastructure --------- Co-authored-by: tomzu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Our release MCM currently has a step for each extension (Toolkit and Q) that requires the human operator to wait and check for the marketplace publish and then try to install from the marketplace. This uses human time and can easily be automated.
Solution
Added a final stage in release pipeline: https://code.amazon.com/reviews/CR-173945904/revisions/1#/commits
that runs this YML build script that automatically installs and uninstalls the extension from marketplace on a two minute interval.
When the version matches the new release version, the code-build succeeds:
When it doesn't, it keeps retrying until the timeout limit is reached (1 hour):
feature/x
branches will not be squash-merged at release time.