Details

    • Sub-task
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • Agent
    • Agent 2017-06-28, Agent 2017-07-12
    • No Action

    Description

      (Initial planned release date: 2017-06-27)

      Tag components

      1) For components that will be updated in this release, check the component pipeline in https://jenkins.puppetlabs.com/view/puppet-agent/view/stable and verify that component pipeline is green

      2) sean.mcdonald: Do the following for each component of the release which has been updated (i.e, puppet, facter, hiera, etc). This is necessary to ensure gems and tarballs are created for each project.

      • Find the component SHA used to create the release candidate puppet-agent package (located in the agent project under configs/<component_name>.json)
      • Create the tag using that release candidate SHA: In the "release-new" Hipchat room: ! tag <repository> <tag> at <long sha> with "message" (ex. ! tag puppet 4.5.1 at 529bdb488a57f9bd135a542882c33c182f02bc8c with "4.5.1")
      • Checkout the newly created tag
      • git describe will show you the tag. Make sure you're building what you think you're building.
      • run bundle exec rake package:implode package:bootstrap pl:jenkins:uber_build to kick the build of the component gem/tarball when you've verified what version you're building (this uses the latest version of the packaging repo to build the packages).

      Attachments

        Activity

          People

            sean.mcdonald Sean McDonald
            geoff.nichols Geoff Nichols
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support