date:20190408

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8213  
 
 
  Error message for certificate name mismatch is clear as mud   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.0.z  
 
 
Fix Version/s: 
 PUP 5.5.z  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1109) Create plugin hook for populating inventory groups dynamically

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1109  
 
 
  Create plugin hook for populating inventory groups dynamically   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 In order to differentiate between dynamically loaded and enumerated nodes groups in the version 2 inventory should support a {{lookups}} key.lookups should be an array of lookups to performEach lookup should have a {{plugin}} field that specifies which plugin to load.The other fields in the lookup should be arbitrary for now.puppetdb pluginWe should implement a {{puppetdb}} lookup plugin that accepts three keys{{u  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For

Jira (BOLT-1109) Create plugin hook for populating inventory groups dynamically

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1109  
 
 
  Create plugin hook for populating inventory groups dynamically   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Summary: 
 Create  `dynamic`  plugin hook for populating  inventory  group attribute  groups dynamically  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1109) Create `dynamic` inventory group attribute

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1109  
 
 
  Create `dynamic` inventory group attribute   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 This adds new attributes to {{Bolt::Inventory::Group}} called {{dynamic}} and {{data_paths}}, which if specified on a group will load node information from a json file (specifically a terraform state file) when the function {{inventory_from_json}} is called in a plan.{{dynamic}} is a boolean value which indicates whether the group should generate new inventory when {{inventory_from_json}} is called or not. If it is set to true and has nodes defined the node list should be merged with the dynamic inventory. If it is set to false, then no dynamic inventory should be loaded.{{data_paths}} is an array of data paths represented as an array of selectors to navigate the JSON data to where we can expect to find hostnames to load as inventory.Questions:- Are {{dynamic}}, {{data_paths}}, and {{inventory_from_json}} the write words for what these components are doing?-  "If it is set to true and has nodes defined the node list should be merged with the dynamic inventory" - this seems doable, but if it's complex I think we can say that any nodes listed will be ignored if dynamic is true.- Can we do glob expantion as part of datapaths, so that users don't need to enumerate each specific node?Notes:- Define a 'backend', and path to json file- Use this field for the node name, and this field for the IP - multiple data paths- Define the inputs to the backend, the backend returns an array of node objects- This backend now will return node names- Can we be more prescriptive- Grouping targets vs inventory- Have a separate inventory file that configures the backend to lookup a list of nodes- what is the information needed to turn a tfstate into a list of targets- Without having groups in 'outside' inventory, or globs in inventory, not sure how to 'discover' things in terraform- Can get 'groups' from tf, and put those into inventory groups- For this type of resource, here's how to turn that into a node - then a separate bit that is "for all my resources, put these ones into this group"- Could we use terraform outputs? Describe them as tf outputs in bolt or tf and turn that into a list of nodes.- Can we turn resources into an array or multiple arrasy of IP and alias (hostname), and can we do that with terrforam output syntax or do we need to do it ourselves?- Are outputs calculated at apply, or from the statefile? Apply{code}  - name: dyn dynamic: truedata_paths:  - name:- 'modules'- 0- 'resources'- 'aws_instance.xenial.*'- 'primary'- 'public_dns'config:  transport: ssh{code}

Jira (PUP-8213) Error message for certificate name mismatch is clear as mud

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8213  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error message for certificate name mismatch is clear as mud   
 

  
 
 
 
 

 
 This issue was fixed for puppet network requests in PUP-9457 first released in 6.4.0. However, it is still an issue for puppet 5.5.x and 6.0.x when running with ruby 2.4 or 2.5, which are the versions bundled into the respective puppet-agent packages.. It is also an issue in 6.4.0 for any provider or other extension still calling the legacy Puppet::Network::HttpPool.http_instance and #http_ssl_instance methods. I'll need to submit a different fixes for 5.5.x, 6.0.x and 6.4.x due to the different implementations.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1205) Only configure tasks to use Bolt's ruby interpreter for localhost

2019-04-08 Thread Lucy Wyman (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-1205  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Only configure tasks to use Bolt's ruby interpreter for localhost   
 

  
 
 
 
 

 
 Notes: 
 
Seems more like part of the inventory than part of the transports 
inventory.rb:178 if target name is localhost, add magic stuff and merge with data config 
Should we do local magic if you have local config? not sure 
If you define anything about localhost then no magic - OR - the magic always happens regardless of config / transport 
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1230) Forbid empty URIs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1230  
 
 
  Forbid empty URIs   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/04/08 3:18 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Currenlty targets can have an empty string as the URI which will prevent them from working with most transports. Can we forbid this globally in bolt or should we forbid it at the inventory2 level. It's already forbidden from the puppet `Target` object.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jira (PDB-4335) Bump versions, push directly, and tag (PuppetDB 6.3.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4335  
 
 
  Bump versions, push directly, and tag (PuppetDB 6.3.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Thompson  
 
 
Created: 
 2019/04/08 1:59 PM  
 
 
Due Date: 
2019/04/12 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) (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 before pushing a non-snapshot version and tagging. 
 Perform a test promotion: 
 
With the version still a -SNAPSHOT, and all commmits merged into the release branch, attempt a test promotion by running the "manual promotion kickoff" job. This is to make sure the pipelines will work when the actual tag is promoted. 
 Set the real version for release: 
 
Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. 
 
 
Go into the 'release-new' hipchat room to make yourself a tag 
  ! tag puppetdb  at  with  
 
Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch

Jira (PDB-4333) Merge-up, branch, and create pipelines (PuppetDB 6.3.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4333  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 6.3.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Thompson  
 
 
Created: 
 2019/04/08 1:59 PM  
 
 
Due Date: 
2019/04/09 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS). 
 
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master 
 
 
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/ 
 
 
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/ 
 
 
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches 
 Do merge-ups: 
 
Merge 5.2.x -> 6.0.x 
 
 
Merge

Jira (PDB-4334) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4334  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Thompson  
 
 
Created: 
 2019/04/08 1:59 PM  
 
 
Due Date: 
2019/04/09 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PDB-4336) Check builds, promote to PE (PuppetDB 6.3.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4336  
 
 
  Check builds, promote to PE (PuppetDB 6.3.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Thompson  
 
 
Created: 
 2019/04/08 1:59 PM  
 
 
Due Date: 
2019/04/13 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 
 
Check that all the builds are green. 
 
 
Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job. 
 
 
Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. 
 
 
Remember to revert pe-puppetdb-extensions to reading the version from the file

Jira (PDB-4337) Update winston (PuppetDB 6.3.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4337  
 
 
  Update winston (PuppetDB 6.3.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eric Thompson  
 
 
Created: 
 2019/04/08 1:59 PM  
 
 
Due Date: 
2019/04/17 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Update winston to make these tickets more accurate for next time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jira (PUP-9634) Update Confluence and JIRA based on release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9634

Update Confluence and JIRA based on release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:57 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

(Initial planned release date: 2019-04-16) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the

Jira (PUP-9633) Send release announcement (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9633  
 
 
  Send release announcement (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Sara Meisburger  
 
 
Created: 
 2019/04/08 1:57 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - 
 
Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. 
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.4.1 is now available".

Jira (PUP-9635) Communicate scope and timeline of next release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9635

Communicate scope and timeline of next release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:57 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

(Initial planned release date: 2019-04-16) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.

Jira (PUP-9631) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9631  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:56 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9630) Prepare release announcement (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9630  
 
 
  Prepare release announcement (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Bill Tang  
 
 
Created: 
 2019/04/08 1:56 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9632) Publish documentation and updates and release notes (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9632  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:56 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Merge the PR linked by Jean Bond. This kicks off a build to publish the docs, which takes some time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9627) Prepare JIRA and Confluence for release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9627

Prepare JIRA and Confluence for release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:55 PM

Due Date:
2019/04/10

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

(Initial planned release date: 2019-04-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.4.1 and puppet-agent 6.4.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y

Jira (PUP-9626) Puppet Platform 6.4.1 Release - 2019-04-16

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9626  
 
 
  Puppet Platform 6.4.1 Release - 2019-04-16
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:55 PM  
 
 
Due Date: 
2019/04/16 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 Puppet Platform 6.4.1 Release - 2019-04-16  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jira (PUP-9628) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9628  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:55 PM  
 
 
Due Date: 
2019/04/10 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9629) Prepare documentation updates and release notes (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9629  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:55 PM  
 
 
Due Date: 
2019/04/12 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9624) Update Confluence and JIRA based on release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9624

Update Confluence and JIRA based on release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:39 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

Jira (PUP-9625) Communicate scope and timeline of next release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9625

Communicate scope and timeline of next release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:39 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

Jira (PUP-9623) Send release announcement (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9623  
 
 
  Send release announcement (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Sara Meisburger  
 
 
Created: 
 2019/04/08 1:38 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - 
 
Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. 
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.4.1 is now available".

Jira (PUP-9621) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9621  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:38 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9622) Publish documentation and updates and release notes (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9622  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:38 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Merge the PR linked by Jean Bond. This kicks off a build to publish the docs, which takes some time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9619) Prepare documentation updates and release notes (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9619  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:37 PM  
 
 
Due Date: 
2019/04/12 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9617) Prepare JIRA and Confluence for release (Puppet Platform 6.4.1)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9617

Prepare JIRA and Confluence for release (Puppet Platform 6.4.1)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:37 PM

Due Date:
2019/04/10

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

Jira (PUP-9620) Prepare release announcement (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9620  
 
 
  Prepare release announcement (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Bill Tang  
 
 
Created: 
 2019/04/08 1:37 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9618) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9618  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.1)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:37 PM  
 
 
Due Date: 
2019/04/10 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9616) Puppet Platform 6.4.1 Release - 2019-04-16

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9616  
 
 
  Puppet Platform 6.4.1 Release - 2019-04-16
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:37 PM  
 
 
Due Date: 
2019/04/16 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 Puppet Platform 6.4.1 Release - 2019-04-16  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jira (PUP-9615) Communicate scope and timeline of next release (Puppet Platform 6.0.8)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9615

Communicate scope and timeline of next release (Puppet Platform 6.0.8)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:22 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

Jira (PUP-9611) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9611  
 
 
  Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:21 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9612) Publish documentation and updates and release notes (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9612  
 
 
  Publish documentation and updates and release notes (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:21 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Merge the PR linked by Jean Bond. This kicks off a build to publish the docs, which takes some time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9614) Update Confluence and JIRA based on release (Puppet Platform 6.0.8)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9614

Update Confluence and JIRA based on release (Puppet Platform 6.0.8)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:22 PM

Due Date:
2019/04/17

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

Jira (PUP-9613) Send release announcement (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9613  
 
 
  Send release announcement (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Sara Meisburger  
 
 
Created: 
 2019/04/08 1:21 PM  
 
 
Due Date: 
2019/04/16 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - 
 
Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. 
If this release has security implications, also send to puppet-security-annou...@googlegroups.com. 
Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.0.8 is now available".

Jira (PUP-9607) Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)

Title: Message Title

Nirupama Mantha created an issue

Puppet / PUP-9607

Prepare JIRA and Confluence for release (Puppet Platform 6.0.8)

Issue Type:
Task

Assignee:
Nirupama Mantha

Created:
2019/04/08 1:20 PM

Due Date:
2019/04/10

Labels:
release

Priority:
Normal

Reporter:
Nirupama Mantha

(Initial planned release date: 2019-04-16) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.0.8 and puppet-agent 6.0.8 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y

Jira (PUP-9608) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9608  
 
 
  Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:20 PM  
 
 
Due Date: 
2019/04/10 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9606) Puppet Platform 6.0.8 Release - 2019-04-16

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9606  
 
 
  Puppet Platform 6.0.8 Release - 2019-04-16
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Nirupama Mantha  
 
 
Created: 
 2019/04/08 1:20 PM  
 
 
Due Date: 
2019/04/16 
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 Puppet Platform 6.0.8 Release - 2019-04-16  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

Jira (PUP-9610) Prepare release announcement (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9610  
 
 
  Prepare release announcement (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Bill Tang  
 
 
Created: 
 2019/04/08 1:20 PM  
 
 
Due Date: 
2019/04/15 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (PUP-9609) Prepare documentation updates and release notes (Puppet Platform 6.0.8)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nirupama Mantha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9609  
 
 
  Prepare documentation updates and release notes (Puppet Platform 6.0.8)   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Jean Bond  
 
 
Created: 
 2019/04/08 1:20 PM  
 
 
Due Date: 
2019/04/12 
 
 
Labels: 
 release  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Nirupama Mantha  
 

  
 
 
 
 

 
 (Initial planned release date: 2019-04-16) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

Jira (BOLT-1220) Build and test bolt-server on el-8

2019-04-08 Thread Cas Donoghue (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue commented on  BOLT-1220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build and test bolt-server on el-8   
 

  
 
 
 
 

 
 The current open PR against bolt-vanagon https://github.com/puppetlabs/bolt-vanagon/pull/89/commits/97a2ffa2f86079dbd338e9302243d51939c157b9 has some code to disable shebang mangling for some ruby code that I added and tested pre vanagon 0.15.22 release ( https://github.com/puppetlabs/vanagon/commit/4b8a98f37eb22208e677f248d6f5f0f59813fd65 ) I would like to  1. make sure that it still works with new version, and 2. see if the upstream changes make excluding shebang mangling unnecessary.  I plan on testing that this afternoon. Once I do that I will ping you for a review. Thanks.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1220) Build and test bolt-server on el-8

2019-04-08 Thread Sara Meisburger (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sara Meisburger commented on  BOLT-1220  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build and test bolt-server on el-8   
 

  
 
 
 
 

 
 Cas Donoghue how's this going? Can release do anything to help move it along?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (BOLT-1200) Localhost target should supply the puppet-agent feature

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1200  
 
 
  Localhost target should supply the puppet-agent feature   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 
 
Assignee: 
 Alex Dreyer Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9587) Serial execution with puppet device and ciscopuppet fails

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9587  
 
 
  Serial execution with puppet device and ciscopuppet fails   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Release Notes Summary: 
 puppet device would not manage multiple network devices in a single run. This was a regression introduced in 6.0.5  due to PUP-8766.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-9587) Serial execution with puppet device and ciscopuppet fails