Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-438

Produce puppetserver 2.0.0-rc2

    XMLWordPrintable

    Details

    • Template:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server Emerald 2015-03-18

      Description

      NOTE: Decision made to go to 2.0.0-rc2 because 2.0.0-rc1 was pushed into Nexus as a non-snapshot build and we don't trust Nexus to handle different artifacts with the same version identifier.

      This is the next most critical step along the wonderful and glorious path to 2.0.0.

      Once the master branch of puppetserver is fully green for EL-7, we need to produce a 2.0.0-rc2 build. This entails:

      1. Wayne Warren will update the master branch pipeline to accept a git SHA parameter as a manual job with no other triggers.

      2. Jeff McCune Will submit a PR to bump the version identifier for the project to 2.0.0-rc2 (note the hypen, this is very specific and confirmed with Kylo Ginsberg) This PR should only be merged if the master branch is fully green following the merge into master of https://github.com/puppetlabs/puppet-server/pull/432

      3. Once built, Jeff will submit another PR to return the version identifier to 2.0.0-SNAPSHOT.

      4. Finally, make sure to add an annotated git tag named 2.0.0-rc2 with the exact SHA that brings in the 2.0.0-rc2 version identifier.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jeff Jeff McCune
              QA Contact:
              Erik Dasher
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support