Add documentation and Cloud Build configs for releasing the recovery tool. #53
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
jiggoha
changed the title
jiggoha
force-pushed
the
recovery_release
branch
from
267fcc7 to
f07f65c
Compare
AlCutter
reviewed
Jan 8, 2024
AlCutter
approved these changes
Jan 8, 2024
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.
This adds a presubmit trigger which should run automatically on each push and a CI trigger which should be invoked manually when we want to test releasing the recovery tool. Unlike the Trusted Applet/OS release process, both the CI and prod (not added in this PR) configs should be invoked manually, because we do not expect to update the recovery tool often.
#55 pins the
ARMORY_UMS_VERSION, sogit_commit_fingerprintof this repo should capture the state of the armory-ums repo in our manifest after it is merged.