[SERVER-524] Set repo-target to PC1 for 2.0 release Created: 2015/03/27  Updated: 2018/04/03  Resolved: 2015/04/02

Status: Closed
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: SERVER 2.0.0

Type: Task Priority: Normal
Reporter: Past Haus Assignee: Jeff McCune
Resolution: Fixed Votes: 0
Labels: AIO, updated_release_notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
blocks SERVER-480 puppetserver 2.0.0 2015-03-31 Release Closed
relates to EZ-34 Add option to ezbake to allow apt_rep... Closed
Story Points: 1
Sprint: RE 2015-04-08
Release Notes: New Feature
QA Contact: Erik Dasher


In order for the puppetserver build to make it into the PC1 repository for the 2.0.0 release, repo-target will need to be set to PC1 in project.clj under the ezbake options.

Comment by Past Haus [ 2015/03/27 ]

This will require an ezbake release to ensure https://github.com/puppetlabs/ezbake/commit/564b9bbb8483afb18d41bf2001d81027b8328f34 is available.

Comment by Past Haus [ 2015/03/30 ]

The ezbake work was released in 0.3.2.

Comment by Jeff McCune [ 2015/04/02 ]

I've confirmed that puppetserver is now landing in the new sub-directory of http://builds.puppetlabs.lan/puppetserver/2.0.0.SNAPSHOT.2015.04.02T0121/repos/el/7/PC1/

Marking as resolved.

Comment by Jeff McCune [ 2015/04/13 ]

*Release Notes*

Setting the release notes to New Feature because this ticket roughly captures the work that went into moving the location of our packages from the previous location at the puppetlabs product repository to the new location of "Puppet Collection 1"

The new location will have a new set of instructions associated with the "Using the Puppet Labs Package Repositories."

This information will reflect the same changes being made for the all in one puppet agent package for Puppet 4.0.

We briefly mention the repository location change in the pre-docs at https://github.com/puppetlabs/pre-docs/pull/50/files#diff-1b283e618df97b0797e826397b3bd2dcR32

Generated at Sat Sep 26 15:50:55 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.