[Promotion] Release manager script #16661
Draft
+1,125
−0
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
This was referenced Feb 21, 2025
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.
Related to #16640
Introducing release/manager.sh script which is a new interface for promotion of debian and docker packages. After internal discussion with decided that packages.o1test.net should be more protected from possible CI code issues which can influence performance of our debian repository. Previously we disabled pushing to debian packages on nightly here #16643 . Next step would be to disable pushing to pacages.o1test.net () and finally lay groundwork for release/manager script:
All above PRs are meant to disallow pushing to packages.o1test.net repository from CI . Enable debian repo management only from script which will be locally executed. This also considers dockers rettagging, but it's done more for consistency as usually we are promoting both debian and docker in the same time. Docker retagging is pretty safe operation as only addition is allowed