Jira (PDB-4921) Check builds, promote to PE (PuppetDB 5.2.19)

[Morgan Rhodes (Jira)]

Morgan Rhodes updated an issue

PuppetDB / PDB-4921 Check builds, promote to PE (PuppetDB 5.2.19) Change By: Morgan Rhodes Epic Link: PUP-10690 Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Morgan Rhodes (Jira)]

Morgan Rhodes created an issue

PuppetDB / PDB-4921 Check builds, promote to PE (PuppetDB 5.2.19)

Issue Type: Task Assignee: Rob Browning Created: 2020/10/07 3:34 PM Due Date: 2020/10/09 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-10-20) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/]. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file

Add Comment

[Austin Blatt (Jira)]

Austin Blatt updated an issue

PuppetDB / PDB-4921 Check builds, promote to PE (PuppetDB 5.2.19)

Change By: Austin Blatt

(Initial planned release date: 2020-10-20)

* Check that all the builds are green. * Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. * If a release branch has already been cut Rebuild the [pacakge promotion job|https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master/job/enterprise_enterprise-dist_packaging_promotion/] with the release branch set instead of master or 2018.1.x. * Once it's promoted to the release branch checkout the release branch of [enterprise-dist|https://github.com/puppetlabs/enterprise-dist] locally and verify that all platforms have the same tagged version of pe-puppetdb

bundle exec rake report:packages

* If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/]. * Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release.   * Remember to revert pe-puppetdb-extensions to reading the version from the file

Add Comment