Skip to content
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

release: split release process #98240

Merged
merged 1 commit into from
Apr 5, 2023
Merged

Conversation

rail
Copy link
Member

@rail rail commented Mar 8, 2023

Previously, the release publishing step contained building, signing and other operations that can happen in advance.

This PR splits the release process into 2 steps: build/sign and publishing. Artifacts generated during the build stage are published to a "staged" bucket and copied to the final bucket during the publishing phase.

  • Extracted docker verification into a function.
  • The version is read from a file now.
  • Use gsutil in MacOS signing in order to download from private repos.
  • Removed PRE_RELEASE variable set from TeamCity in favour of "guessing" it from the version.
  • Simplified dry-run logic to define version/build names, because the version is defined in the source code now.
  • The publishing phase updates docker image packages.

Epic: RE-307
Fixes: RE-211
Release note: None

@rail rail added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-release T-release Release Engineering & Automation Team labels Mar 8, 2023
@rail rail requested review from jlinder and celiala March 8, 2023 19:19
@rail rail requested a review from a team as a code owner March 8, 2023 19:19
@rail rail self-assigned this Mar 8, 2023
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rail rail force-pushed the split-release-3 branch 2 times, most recently from aefe603 to f9e6b3d Compare March 13, 2023 21:20
@rail
Copy link
Member Author

rail commented Mar 13, 2023

I think this is ready to go! I tested it and so far it works as expected.

@rail rail force-pushed the split-release-3 branch from f9e6b3d to 447e730 Compare March 14, 2023 01:06
@rail rail force-pushed the split-release-3 branch 2 times, most recently from c029def to 66d441f Compare March 27, 2023 21:36
@rail rail changed the title release: spit release process release: split release process Mar 28, 2023
@rail rail force-pushed the split-release-3 branch from 66d441f to 6859cbf Compare April 3, 2023 01:27
Copy link
Collaborator

@jlinder jlinder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple file name change notes. Then LGTM!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested file name for the copied version of this file:

sign_macos_staged_release.sh

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested file name:

publish-staged-cockroach-release.sh

Previously, the release publishing step contained building, signing and
other operations that can happen in advance.

This PR splits the release process into 2 steps: build/sign and
publishing. Artifacts generated during the build stage are published to
a "staged" bucket and copied to the final bucket during the publishing
phase.

* Extracted docker verification into a function.
* The version is read from a file now.
* Use `gsutil` in MacOS signing in order to download from private repos.
* Removed `PRE_RELEASE` variable set from TeamCity in favour of
  "guessing" it from the version.
* Simplified dry-run logic to define version/build names, because the
  version is defined in the source code now.
* The publishing phase updates docker image packages.

Epic: RE-307
Fixes: RE-211
Release note: None
@rail rail force-pushed the split-release-3 branch from 6859cbf to 196c333 Compare April 5, 2023 15:36
@rail
Copy link
Member Author

rail commented Apr 5, 2023

bors r=jlinder

@craig
Copy link
Contributor

craig bot commented Apr 5, 2023

Build succeeded:

@craig craig bot merged commit 2428a0b into cockroachdb:master Apr 5, 2023
@rail rail added the backport-23.1.x Flags PRs that need to be backported to 23.1 label Apr 5, 2023
@rail
Copy link
Member Author

rail commented Apr 5, 2023

blathers backport release-23.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-release backport-23.1.x Flags PRs that need to be backported to 23.1 C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-release Release Engineering & Automation Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants