[CT-423] [Feature] Make release process testable

iknox-fa commented 2 years ago

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature

We have been repeatedly caught off guard by bugs in the release process that don't manifest until an actual release. To prevent this we need a method to test them regularly.

Ideas:

A dry-run mode that does everything except the final push
Running locally via Nektos/act
Creating a test runner to integrate GHAs with pyTest so the release process can be tested as part of the current test suite (or in it's own test suite)
Service checks at release start time to ensure the necessary systems are reachable and functional.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

github-actions[bot] commented 2 years ago

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

emmyoop commented 9 months ago

I'd call this done! We run nightly tests and can manually test releases.

dbt-labs / dbt-core