Pulp

I believe this is the task we need to work on next in terms of improving our release automation.

Background¶

Currently, at a high level, our workflow is this:

0. Release person tags the release and pushes to the repo
1. Release person triggers a release
2. The release workflow runs the tests
3. If the tests all pass, the release workflow builds the artifacts and then publishes them.

The artifacts include the pypi package, the bindings (ruby and python), and the docs.

New Workflow¶

I'd propose we create the following workflow:

1. Release person triggers a release
2. The release automation creates the tag and artifacts (note: this step does not push/publish the tag or artifacts)
3. The release automation runs the tests against these artifacts
4. If the tests pass, the release automation pushes the tag and the artifacts

I believe step 2 should also check for a pre-existing tag and use it if it already exists. This would allow the workflow to be idempotent. The scripts that publish the artifacts in step 4 are already idempotent.

I think this change to our workflow will help us to move toward the unified release pipeline where we can also test against the installer, etc as well.