Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

(maint) Add docs for release process #48

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

(maint) Add docs for release process #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1,15 @@
# razor-vanagon

## How to promote to PE

1. Tag razor-server with the correct version (using Kerminator).
1. Pin razor-vanagon to that version in configs/components/razor-server.json. Commit this to master.
1. Tag razor-vanagon with the SHA of the commit above (using Kerminator).

Git automation will generate pe-razor-server packages, then promote those packages into the latest version of PE.
Copy link
Contributor

Choose a reason for hiding this comment

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

Did you set up automation to do this? because I'm not aware of any webhooks or anything set up to build pe-razor-server automatically.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Isn't that the "razor-suite (master) PE Suite Pipeline Step 06 -- Vanagon Project Integration" step here: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/Razor/

I'm unclear on how releases happen for FOSS, i.e. how we add to GitHub's Releases page. I'd like that to be in this doc as well.

Copy link
Contributor

Choose a reason for hiding this comment

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

ahh okay, yeah, looks like https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/Razor/job/platform_razor-suite_razor-vanagon-suite-init_pe_suite_master/ (the most upstream job) does poll. I just didn't know that was set up. 😊
so yeah, this is accurate.

The FOSS release process is in winston (https://github.com/puppetlabs/winston/blob/master/files/razor/server/release_ticket_descriptions.yaml) but looks like it's a bit out of date. Do you want those instructions in this doc as well or would it be better to just add instructions for generating winston tickets and just keeping the process up-to-date in that one place?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm happy to link directly to that in this doc, so it only lives in one place.


### If the release branch has already been cut

Once the pe-razor-server packages [appear](builds.puppetlabs.lan/pe-razor-server), run the [Package Promotion Job](https://jenkins-compose.delivery.puppetlabs.net/view/Promotion/job/Package-Promotion/build?delay=0sec) using the release branch name as the `BRANCH` parameter.

Verify promotion by issuing `pelist <release_branch_title>` to Kerminator or checking enterprise-dist's commit history for the release branch on GitHub.