Document the release tag back-fill script. #17808
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
jsirois
added
the
category:internal
benjyw
approved these changes
Dec 14, 2022
jsirois
added a commit
to jsirois/pants
that referenced
this pull request
Dec 15, 2022
(cherry picked from commit 2dc4c1b)
jsirois
added a commit
to jsirois/pants
that referenced
this pull request
Dec 15, 2022
(cherry picked from commit 2dc4c1b)
jsirois
added a commit
that referenced
this pull request
Dec 15, 2022
…17808) (#17814) Cherry-pick the new release workflow for mapping release tags to commits. This is 3 stacked cherry-picks, all clean: commit 4841e8b (HEAD -> release_tag_mapping/tools/CPs, origin/release_tag_mapping/tools/CPs) Author: John Sirois <[email protected]> Date: Wed Dec 14 14:18:38 2022 -0800 Document the release tag back-fill script. (#17808) (cherry picked from commit 2dc4c1b) commit bca29f6 Author: John Sirois <[email protected]> Date: Wed Dec 14 13:21:01 2022 -0800 Add a release tag backfill script. (#17806) The new script was used to successfully backfill all Pants release tag mappings to S3 and the release workflow is fixed to scope its sync to just tags and the underlying helper deploy_to_s3.py code to skip index.html generation when there is no data to generate it from. (cherry picked from commit a837b35) commit 2922d74 Author: John Sirois <[email protected]> Date: Wed Dec 14 07:26:53 2022 -0800 Set up release tag mapping workflow. (#17801) This will establish an `https://binaries.pantsbuild.org/tags/pantsbuild.pants/release_*` file for each `release_*` tag pushed. The file will contain the tagged commit's sha for use by `scie-pants` in setting up the proper `--find-links` repo for the purposes of installing that Pants version. After manually running this workflow for a few old release tags, an automated backfill (seperate script forthcoming) will be run. See commentary in pantsbuild/scie-pants#1 (cherry picked from commit 340f736)
jsirois
added a commit
that referenced
this pull request
Dec 15, 2022
…17808) (#17815) Cherry-pick the new release workflow for mapping release tags to commits. This is 3 stacked cherry-picks, all clean: commit 4841e8b (HEAD -> release_tag_mapping/tools/CPs, origin/release_tag_mapping/tools/CPs) Author: John Sirois <[email protected]> Date: Wed Dec 14 14:18:38 2022 -0800 Document the release tag back-fill script. (#17808) (cherry picked from commit 2dc4c1b) commit bca29f6 Author: John Sirois <[email protected]> Date: Wed Dec 14 13:21:01 2022 -0800 Add a release tag backfill script. (#17806) The new script was used to successfully backfill all Pants release tag mappings to S3 and the release workflow is fixed to scope its sync to just tags and the underlying helper deploy_to_s3.py code to skip index.html generation when there is no data to generate it from. (cherry picked from commit a837b35) commit 2922d74 Author: John Sirois <[email protected]> Date: Wed Dec 14 07:26:53 2022 -0800 Set up release tag mapping workflow. (#17801) This will establish an `https://binaries.pantsbuild.org/tags/pantsbuild.pants/release_*` file for each `release_*` tag pushed. The file will contain the tagged commit's sha for use by `scie-pants` in setting up the proper `--find-links` repo for the purposes of installing that Pants version. After manually running this workflow for a few old release tags, an automated backfill (seperate script forthcoming) will be run. See commentary in pantsbuild/scie-pants#1 (cherry picked from commit 340f736)
Merged
stuhood
added a commit
that referenced
this pull request
Dec 17, 2022
### Internal * Get rid of `_ToolLockfileMixin`. ([#17823](#17823)) * Fix `build-support/bin/deploy_to_s3.py`. ([#17818](#17818)) * Upgrade setproctitle to 1.3.2 ([#17804](#17804)) * Document the release tag back-fill script. ([#17808](#17808)) * Add a release tag backfill script. ([#17806](#17806)) * Set up release tag mapping workflow. ([#17801](#17801)) * go: fix path lookup for copied header files ([#17798](#17798)) * go: set `replace_sandbox_root_in_args=True` since replacement is used ([#17797](#17797)) * go: set missing `Goal.environment_behavior` on a debug goal ([#17799](#17799)) * go: rename option to --go-test-coverage-packages ([#17795](#17795)) * A stub page for dep validation docs. ([#17788](#17788)) * Upgrade to newest remote execution proto ([#17786](#17786)) * Adding tests for `cc` dependency inference showing source roots as `include_directories` ([#17738](#17738)) * Fix validation of release PEXes. ([#17785](#17785)) * Unconditionally register export-codegen goal in pants.core ([#17782](#17782)) * go: allow exporting cgo codegen for third party packages ([#17770](#17770)) * Properly set `pex_root` when running python sources in-sandbox. ([#17750](#17750)) * Renames `output_files` and `output_directories` fields for `experimental_shell_command` ([#17744](#17744))
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.
No description provided.