Jira (PDB-5586) Bump versions, push directly, and tag (Puppet Platform 7.23.0)

tefoji (Jira)

unread,

Jan 31, 2023, 4:04:02 PM1/31/23

to puppe...@googlegroups.com

tefoji updated an issue

PuppetDB /

PDB-5586

Bump versions, push directly, and tag (Puppet Platform 7.23.0)

Change By:	tefoji
Epic Link:	PUP-11740

Add Comment

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)

tefoji (Jira)

unread,

Jan 31, 2023, 4:04:03 PM1/31/23

to puppe...@googlegroups.com

tefoji created an issue

PuppetDB /

PDB-5586

Bump versions, push directly, and tag (Puppet Platform 7.23.0)

Issue Type:	Task
Assignee:	Joshua Partlow
Created:	2023/01/31 1:03 PM
Due Date:	2023/02/03
Priority:	Normal
Reporter:	tefoji

(Initial planned release date: 2023-02-07)

(if you're making the first release off a new branch you may already have done some of this)

Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions
match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging.

Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is
the same clj-parent version that puppetserver will release with.

Disable automatic promotions:

If a PE release branch has not been cut, disable automatic promotions on the branch(es) you are releasing from.
This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example.

Run the `tag-release` command:

Change to a clean checkout of the relevant `puppetdb` branch
(e.g. 6.x, main, ...).

Run the `tag-release` script. This example is automatically
generated, assuming we're doing an N.x release, so you may
need to adjust it, and will have to adjust it if we're
releasing main:

  PDB_PATH=/some/where/src/pdb \

  PDB_EXT_PATH=/some/where/pdbext \

  PDB_GIT_REMOTE=origin \

  PDB_EXT_GIT_REMOTE=origin \

  ext/bin/tag-release <git-branch> 7.12.1

The command should prompt you before making any changes to the
remote repository, and you can inspect the pending changes
(to your local repositories) at that point if you like.