Python staged releases: centralized staged upload #11187
Merged
+101
−17
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.
Logic is partially duplicated with #11179, but given there were some constraint on the Python code and I wanted to avoid risk, those will be for now independent.
To be looked at properly, especially for when Python will move out of core.
Centralized upload is NOT properly tested.
My idea is that once this is merged, the first nightly run to follow will build all relevant artifacts and (if no tests fails in the meantime, not exactly a given) and the automatic upload will be triggered.
If not, it can be triggered (and tested) by an admin the day after.