[SERVER-415] Continually bump puppet-server dependency on puppet-agent as AIO progresses Created: 2015/03/04  Updated: 2018/04/03  Resolved: 2015/03/16

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

Type: Task Priority: Normal
Reporter: Jeremy Barlow Assignee: Jeff McCune
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by SERVER-455 Fix ruby spec failure on version bump Closed
Cloners
is cloned by SERVER-476 Continually bump puppet-server depend... Closed
Relates
relates to SERVER-412 Get Pup4/Pup-Svr2 acceptance tests pa... Closed
Template:
Epic Link: Green: Puppet 4.0 Changes
Sub-team: emerald
Story Points: 3
Sprint: Server Emerald 2015-03-18
QA Contact: Erik Dasher

 Description   

This ticket covers all of the work involved in periodically bumping the puppet-server's dependency on puppet-agent in CI to track the HEAD of the AIO branch. This should be bound within the course of the current sprint, with another to replace it if needed when the next sprint is kicked off.



 Comments   
Comment by Jeff McCune [ 2015/03/13 ]

We need to bump up to a puppet-agent package that includes the changes in RE-4141 and the general "package provides" changes prior to rc2.

Comment by Jeff McCune [ 2015/03/16 ]

Pull request to bring our dependency on Puppet Agent up to 2.0.0-rc1 is at https://github.com/puppetlabs/puppet-server/pull/452

Comment by Jeff McCune [ 2015/03/16 ]

Assigning back to me until SERVER-455 gets merged in.

Comment by Jeff McCune [ 2015/03/16 ]

Bumped to use puppet-agent 4.0.0-rc1 this sprint.

Generated at Sat Sep 19 11:30:20 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.