Jira (PDOC-241) html output breaks on multiple function signatures

2018-04-23 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-241  
 
 
  html output breaks on multiple function signatures   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 Screen Shot 2018-04-23 at 9.25.52 AM.png  
 
 
Created: 
 2018/04/23 1:26 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 Running puppet strings generate on the following function:  
 
 
 
 
 # @summary overview string  
 
 
 Puppet::Functions.create_function(:dope) do  
 
 
   # This is a summary  
 
 
   #  
 
 
   # @author  
 
 
   #  the author of this class  
 

Jira (PDOC-242) Markdown TOC should display summary or nothing

2018-04-23 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-242  
 
 
  Markdown TOC should display summary or nothing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/23 1:32 AM  
 
 
Labels: 
 beginner  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Eric Putnam  
 

  
 
 
 
 

 
 Currently, after each class, type, function, task, or plan name in the table of contents, Strings writes either the text from the @summary tag or the first 140 characters of the "overview" text. This ticket is to display the @summary tag or nothing at all, as a clipped overview may be nothing more than clutter in the table of contents.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

Jira (PDOC-239) In the class list in REFERENCE.md, the class description is cut off

2018-04-23 Thread Eric Putnam (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Putnam assigned an issue to Eric Putnam  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Strings /  PDOC-239  
 
 
  In the class list in REFERENCE.md, the class description is cut off   
 

  
 
 
 
 

 
Change By: 
 Eric Putnam  
 
 
Resolution: 
 Done  
 
 
Assignee: 
 Eric Putnam  
 
 
Status: 
 Open Resolved  
 

  
 
 
 
 

 
 
 

 
 
 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-7051) Static catalog compiler uses Puppet master hostname for %H in fileserver config

2018-04-23 Thread JIRA
Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthias Hörmann commented on  PUP-7051  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Static catalog compiler uses Puppet master hostname for %H in fileserver config   
 

  
 
 
 
 

 
 Is there any progress on this? As long as this bug exists the static catalog compiler is basically useless to us.  
 

  
 
 
 
 

 
 
 

 
 
 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-8668) Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver

2018-04-23 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8668  
 
 
  Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Team: 
 Platform OS  
 

  
 
 
 
 

 
 
 

 
 
 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-8667) resource 'tidy' should be less chatty

2018-04-23 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8667  
 
 
  resource 'tidy' should be less chatty   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 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-8666) `puppet help lookup` does not indicate that you can use puppet settings

2018-04-23 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8666  
 
 
  `puppet help lookup` does not indicate that you can use puppet settings   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Team: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 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-8634) Chown of ssldir Causing Failures

2018-04-23 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8634  
 
 
  Chown of ssldir Causing Failures   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Assignee: 
 Geoff Nichols  
 

  
 
 
 
 

 
 
 

 
 
 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-8667) resource 'tidy' should be less chatty

2018-04-23 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig assigned an issue to Jacob Helwig  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8667  
 
 
  resource 'tidy' should be less chatty   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Assignee: 
 Jacob Helwig  
 

  
 
 
 
 

 
 
 

 
 
 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-8668) Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver

2018-04-23 Thread Geoff Nichols (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Geoff Nichols updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8668  
 
 
  Installing puppet-agent 5.5.1 together with puppetserver 2.8.1 breaks puppetserver   
 

  
 
 
 
 

 
Change By: 
 Geoff Nichols  
 
 
Team: 
 Platform  OS  Core  
 

  
 
 
 
 

 
 
 

 
 
 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-2782) Yumrepo target attribute does not work

2018-04-23 Thread Jacob Helwig (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jacob Helwig assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2782  
 
 
  Yumrepo target attribute does not work   
 

  
 
 
 
 

 
Change By: 
 Jacob Helwig  
 
 
Assignee: 
 Eric Delaney  
 

  
 
 
 
 

 
 
 

 
 
 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-463) Migration docs to include moving from mco to orchestrator

2018-04-23 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi commented on  BOLT-463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migration docs to include moving from mco to orchestrator   
 

  
 
 
 
 

 
 Michael Smith I just talked to Kate Lopresti she said you guys reviewed this last week, do you want to be assigned to this ticket or should the ticket be closed?  
 

  
 
 
 
 

 
 
 

 
 
 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-8673) Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version

2018-04-23 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson commented on  PUP-8673  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version   
 

  
 
 
 
 

 
 You are technically correct (the best kind of correct!). Read on in the same paragraph though: 
 
Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API.
 There will be more 5.x releases before 6.x removes this, and it seemed better to get the warnings in early rather than wait for a 5.6.0 to introduce them, or to call this release 5.6.0 solely due to the inclusion of a new deprecation.  
 

  
 
 
 
 

 
 
 

 
 
 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-8673) Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version

2018-04-23 Thread Eric Sorenson (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Sorenson assigned an issue to Eric Sorenson  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8673  
 
 
  Puppet 5.5.1 should not have changed the Ruby deprecations - deprecations should be introduced in a new minor version   
 

  
 
 
 
 

 
Change By: 
 Eric Sorenson  
 
 
Assignee: 
 Eric Sorenson  
 

  
 
 
 
 

 
 
 

 
 
 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-463) Migration docs to include moving from mco to orchestrator

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-463  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Migration docs to include moving from mco to orchestrator   
 

  
 
 
 
 

 
 I think they're still in progress, I don't know that I'd close this yet.  
 

  
 
 
 
 

 
 
 

 
 
 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-463) Migration docs to include moving from mco to orchestrator

2018-04-23 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-463  
 
 
  Migration docs to include moving from mco to orchestrator   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Sprint: 
 Bolt  Ready for Grooming  Kanban  
 

  
 
 
 
 

 
 
 

 
 
 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-463) Migration docs to include moving from mco to orchestrator

2018-04-23 Thread Yasmin Rajabi (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasmin Rajabi assigned an issue to Michael Smith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-463  
 
 
  Migration docs to include moving from mco to orchestrator   
 

  
 
 
 
 

 
Change By: 
 Yasmin Rajabi  
 
 
Assignee: 
 Michael Smith  
 

  
 
 
 
 

 
 
 

 
 
 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-8674) Forge the One Ring authorization handler to rule them all

2018-04-23 Thread Charlie Sharpsteen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Charlie Sharpsteen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8674  
 
 
  Forge the One Ring authorization handler to rule them all   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/04/23 10:15 AM  
 
 
Environment: 
 As a Puppet Enterprise user I'd like to configure one authorization method (certificate, RBAC token, etc.) that works across all PE apis. Currently, each PE service offers different API authorization choices: 
 
Puppet Server: Provides rich, certificate-based, per-route authorization via auth.conf. Does not support RBAC. 
Code Manager: Only supports RBAC. 
Orchestrator: Only supports RBAC. 
Classifier: Supports RBAC or simple certificate-based "all or nothing" auth. 
PuppetDB: Supports RBAC or simple certificate-based "all or nothing" auth. 
 There are other APIs that offer other choices, but the above summarizes the situation with the most common user-facing endpoints. Note that there is no "common denominator" that works across all services despite PE being an integrated package of software. This sort of situation re-enforces a perception that Puppet Enterprise is overly complicated and difficult to interact with. Proposed Solution We should have one TrapperKeepr authorization service that is used by all PE services and provides a pluggable range of options, for example: 
 
Certificate auth via auth.conf, with all the bells and whistles such as per-route auth and auth based on certificate extensions 
Simple whitelist certificate auth 
RBAC auth 
 FOSS builds could exclude items like RBAC auth, but should still use the same service. Configuration should be consistent and there should be at least one "common denominator" method that is always supported.  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Charlie Shar

Jira (PUP-8672) Memory leak in Puppet Server from loading translations

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  PUP-8672  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Memory leak in Puppet Server from loading translations   
 

  
 
 
 
 

 
 Hard error if you pass a symbol would've also prevented SERVER-2192, so that works for me. I can try to add it to the PR.  
 

  
 
 
 
 

 
 
 

 
 
 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-349) Update release automation to tag bolt-vanagon and publish packages

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-349  
 
 
  Update release automation to tag bolt-vanagon and publish packages   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Acceptance Criteria: 
 A release pipeline that does the gem release, updates bolt-vanagon with the gem version, tags bolt-vanagon, then runs the suite pipeline to build and test packages for the release.  
 

  
 
 
 
 

 
 
 

 
 
 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-349) Update release automation to tag bolt-vanagon and publish packages

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update release automation to tag bolt-vanagon and publish packages   
 

  
 
 
 
 

 
 It'd be nice if it checked that the gem release SHA and SHA in bolt-vanagon match before doing the gem release.  
 

  
 
 
 
 

 
 
 

 
 
 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-348) Add automated tests of system packages

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add automated tests of system packages   
 

  
 
 
 
 

 
 What should the TEST_TARGET include?  
 

  
 
 
 
 

 
 
 

 
 
 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-349) Update release automation to tag bolt-vanagon and publish packages

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-349  
 
 
  Update release automation to tag bolt-vanagon and publish packages   
 

  
 
 
 
 

 
Change By: 
 Michael Smith  
 
 
Assignee: 
 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 (BOLT-348) Add automated tests of system packages

2018-04-23 Thread Michael Smith (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Smith commented on  BOLT-348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add automated tests of system packages   
 

  
 
 
 
 

 
 Waiting on https://github.com/puppetlabs/ci-job-configs/pull/4349 to get fixed.  
 

  
 
 
 
 

 
 
 

 
 
 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-7331) "Unable to set ownership" error with logdest on agents

2018-04-23 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7331  
 
 
  "Unable to set ownership" error with logdest on agents   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 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-7331) "Unable to set ownership" error with logdest on agents

2018-04-23 Thread Craig Gomes (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Gomes updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-7331  
 
 
  "Unable to set ownership" error with logdest on agents   
 

  
 
 
 
 

 
Change By: 
 Craig Gomes  
 
 
Team: 
 Platform Core Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 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-1952) Run specs against jruby

2018-04-23 Thread Patrick Carlisle (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Carlisle assigned an issue to Patrick Carlisle  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1952  
 
 
  Run specs against jruby   
 

  
 
 
 
 

 
Change By: 
 Patrick Carlisle  
 
 
Assignee: 
 Patrick Carlisle  
 

  
 
 
 
 

 
 
 

 
 
 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-416) integrate the Hands-On Lab into the existing documentation

2018-04-23 Thread Kate Lopresti (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kate Lopresti commented on  BOLT-416  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: integrate the Hands-On Lab into the existing documentation   
 

  
 
 
 
 

 
 Added review edits to the content and pushed to fork katelopresti/tasks-hands-on-lab.  
 

  
 
 
 
 

 
 
 

 
 
 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.