Jira (BOLT-429) Create standalone Linux packages
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: Michael Smith 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 (BOLT-429) Create standalone Linux packages
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: Michael Smith 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 (BOLT-429) Create standalone Linux packages
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-429 Create standalone Linux packages Change By: Michael Smith 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-8649) Load vendored modules and execute unit tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8649 Load vendored modules and execute unit tests Change By: Josh Cooper QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed 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-8649) Load vendored modules and execute unit tests
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8649 Load vendored modules and execute unit tests Change By: Josh Cooper Sprint: Platform Core 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 (PUP-8631) --tags should override individual --skip_tags
Title: Message Title Ben Ford commented on PUP-8631 Re: --tags should override individual --skip_tags I think the generalizable solution here is that there should be a way of indicating that --tags and --skip_tags are inverses of each other (or something like inverse) and have the one specified at the more specific scope take precedence. In other words, whichever was specified at the command line would override the other. 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-4678) Enable yumrepo priority attribute to support lower priority than 99
Title: Message Title Melissa Stone commented on PUP-4678 Re: Enable yumrepo priority attribute to support lower priority than 99 I have confirmed this is in puppet-agent 5.5.0.133.ga165edc and behaves as expected 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-462) Function to query puppetdb from plans.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-462 Function to query puppetdb from plans. Change By: Alex Dreyer Users should be able to use the puppetdb_query function from plans.- How do we use bolts own config and token support? (see https://github.com/puppetlabs/bolt/pull/283) - How do we avoid conflicting with the other puppetdb_query function? 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-462) Function to query puppetdb from plans.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-462 Function to query puppetdb from plans. Issue Type: New Feature Assignee: Unassigned Created: 2018/04/09 3:00 PM Priority: Normal Reporter: Alex Dreyer Users should be able to use the puppetdb_query function from plans. How do we use bolts own config and token support? How do we avoid conflicting with the other puppetdb_query function? Add Comment This message was sent by Atlassian
Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Tommy McNeely updated an issue Puppet / PUP-8650 Repository error message uri is missing part of the path Note: Also affects 5.5.0 $ puppet module --debug --module_repository https://artifactory.domain.com/bogus_test/puppet/ search test Debug: Runtime environment: puppet_version=5.5.0, ruby_version=2.4.3, run_mode=user, default_encoding=UTF-8 Notice: Searching https://artifactory.domain.com/bogus_test/puppet/ ... Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Failed to load library 'pe_license' for feature 'pe_license': cannot load such file -- pe_license Debug: HTTP GET https://artifactory.domain.com/bogus_test/puppet//bogus_test/puppet/v3/modules?query=test Error: Request to Puppet Forge failed. The server being queried was https://artifactory.domain.com/v3/modules?query=test The HTTP response we received was '404 Not Found' Error: Try 'puppet help module search' for usage
Jira (PUP-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Sean McDonald updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Sean McDonald Fix Version/s: PUP 5.5.1 Fix Version/s: PUP 6.0.0 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Sean McDonald commented on PUP-8609 Re: Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Kenn Hussey this won't make it for 5.5.1 but that doesn't really matter. The work really just needs to land alongside ruby 2.5 with Puppet 6, so I'll just change the fixversion to that. 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-8650) Repository error message uri is missing part of the path
Title: Message Title Tommy McNeely created an issue Puppet / PUP-8650 Repository error message uri is missing part of the path Issue Type: Bug Affects Versions: PUP 5.3.5 Assignee: Unassigned Created: 2018/04/09 2:43 PM Environment: CentOS 7.4, Puppet Enterprise 2017.3.5 (puppet-agent 5.3.5) Priority: Normal Reporter: Tommy McNeely We had a problem with our artifactory server, where it would return a 404 for the Puppet repository it was providing. This caused an error message to appear, about 404 errors. I tried to install the module manually (or search for it) and also got a 404 error: [root@puppetmaster ~]# puppet module --debug search saz-sudo Debug: Runtime environment: puppet_version=5.3.5, ruby_version=2.4.3, run_mode=user, default_encoding=UTF-8 Notice: Searching https://artifactory.domain.com/artifactory/api/puppet/puppet ...
Jira (PUP-8582) Add vendor_modules to autoloader search path
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8582 Add vendor_modules to autoloader search path Change By: Josh Cooper Assignee: Josh Cooper 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-8581) Extract zone type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8581 Extract zone type/provider into a module Change By: Josh Cooper Assignee: Josh Cooper 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-456) Plans should restrict return types to expected values
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-456 Plans should restrict return types to expected values Change By: Alex Dreyer Release Notes Summary: The run_plan function will no longer allow plans to return values that do not have JSON representations and would cause an error. The plan language now limits the return values of a plan to JSON structures, Error, Result, ResultSet and Target. Release Notes: New Feature 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-454) Plans should return undef without an explicit return
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-454 Plans should return undef without an explicit return Change By: Alex Dreyer Release Notes Summary: Plans will no longer return the value of the last line implicitly. They will return undef unless the return function is called. Release Notes: New Feature 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-461) bolt package conflict on Ubuntu 18.04
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-461 bolt package conflict on Ubuntu 18.04 Change By: Michael Smith Sprint: Bolt Ready for Grooming 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-461) bolt package conflict on Ubuntu 18.04
Title: Message Title Rob Braden commented on BOLT-461 Re: bolt package conflict on Ubuntu 18.04 The Thunderbolt 'bolt' will be in Fedora 28: https://fedoraproject.org/wiki/Changes/ThunderboltEnablement 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-7904) return() documentation incorrect regarding lambdas
Title: Message Title Enis Inan updated an issue Puppet / PUP-7904 return() documentation incorrect regarding lambdas Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-8502) Puppet lookup always includes classes from the ENC
Title: Message Title Enis Inan updated an issue Puppet / PUP-8502 Puppet lookup always includes classes from the ENC Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-8416) Remove old acceptance code that now lives in beaker-puppet
Title: Message Title Enis Inan updated an issue Puppet / PUP-8416 Remove old acceptance code that now lives in beaker-puppet Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-8467) Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver
Title: Message Title Enis Inan updated an issue Puppet / PUP-8467 Starting to get broken pipe (HTTP 500) on certain manifest - gone after restarting puppetserver Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-8364) puppet device apply mode
Title: Message Title Enis Inan updated an issue Puppet / PUP-8364 puppet device apply mode Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-7057) Update password property of User type to mention Sensitive data type
Title: Message Title Enis Inan updated an issue Puppet / PUP-7057 Update password property of User type to mention Sensitive data type Change By: Enis Inan Fix Version/s: PUP 5.3.6 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Enis Inan updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Enis Inan Fix Version/s: PUP 5.3.6 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 (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Enis Inan updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Enis Inan Fix Version/s: FACT 3.9.6 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 (FACT-1504) Uptime resolver fact for Windows uses unreliable metric for uptime
Title: Message Title Enis Inan updated an issue Facter / FACT-1504 Uptime resolver fact for Windows uses unreliable metric for uptime Change By: Enis Inan Fix Version/s: FACT 3.9.6 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 (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX
Title: Message Title Enis Inan updated an issue Facter / FACT-1597 "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX Change By: Enis Inan Fix Version/s: FACT 3.9.6 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 (FACT-1819) Facter.rb is swallowing useful exception details when failing to load libfacter
Title: Message Title Enis Inan updated an issue Facter / FACT-1819 Facter.rb is swallowing useful exception details when failing to load libfacter Change By: Enis Inan Fix Version/s: FACT 3.9.6 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 (FACT-1549) Build CFacter gems in Jenkins
Title: Message Title Enis Inan updated an issue Facter / FACT-1549 Build CFacter gems in Jenkins Change By: Enis Inan Fix Version/s: FACT 3.9.6 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 (FACT-1547) Create a Windows binary facter gem
Title: Message Title Enis Inan updated an issue Facter / FACT-1547 Create a Windows binary facter gem Change By: Enis Inan Fix Version/s: FACT 3.9.6 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-8649) Load vendored modules and execute unit tests
Title: Message Title Josh Cooper created an issue Puppet / PUP-8649 Load vendored modules and execute unit tests Issue Type: Task Assignee: Josh Cooper Created: 2018/04/09 11:52 AM Priority: Normal Reporter: Josh Cooper In preparation for removing non-core types and providers from puppet we are going to move them within the puppet code base to the lib/puppet/vendor/modules directory. We need to: 1. Add each module's lib directory to the ruby load path so the autoloader can still find them 2. When running rake spec and rake parallel:spec we should execute the modules' unit tests as well. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8535) Backport ruby warning rake task
Title: Message Title Enis Inan updated an issue Puppet / PUP-8535 Backport ruby warning rake task Change By: Enis Inan Release Notes: Not Needed 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-8566) "puppet config print" should only emit diagnostic info when run with verbose or higher
Title: Message Title Josh Cooper commented on PUP-8566 Re: "puppet config print" should only emit diagnostic info when run with verbose or higher Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/5d8590cca9d6000d05d0096e4250fe7f70ad5f82 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-461) bolt package conflict on Ubuntu 18.04
Title: Message Title Rob Braden commented on BOLT-461 Re: bolt package conflict on Ubuntu 18.04 We will need to do some magic to properly replace/upgrade from the earlier 'bolt' package without breaking the upstream system 'bolt' packages. 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Ethan Brown Sprint: Windows Grooming 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Ethan Brown assigned an issue to Sean McDonald Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Ethan Brown Assignee: Sean McDonald 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Ethan Brown updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Ethan Brown Team: Windows Platform 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 (BOLT-461) bolt package conflict on Ubuntu 18.04
Title: Message Title Rob Braden created an issue Puppet Task Runner / BOLT-461 bolt package conflict on Ubuntu 18.04 Issue Type: Task Assignee: Unassigned Created: 2018/04/09 11:17 AM Priority: Normal Reporter: Rob Braden Ubuntu 18.04 has a package called 'bolt' as part of the core system: https://packages.ubuntu.com/bionic/bolt We will need to rename our packages to avoid a conflict. Fortunately they do not have a binary called 'bolt' so I think we can retain that, but we'll definitely need to rename the packages. puppet-bolt? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-428) Create bolt-runtime build pipeline
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-428 Create bolt-runtime build pipeline Change By: Michael Smith 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 (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith commented on BOLT-459 Re: Reboot a target and wait for it to become available. I don't know that we need a plan for running from the CLI. I expect most people who want a reboot helper want to use it in a plan and do more things after the reboot has finished. 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-460) Facts module should include Puppet facts
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-460 Facts module should include Puppet facts Issue Type: Improvement Assignee: Unassigned Created: 2018/04/09 9:44 AM Priority: Normal Reporter: Michael Smith The facts module should include Puppet-specific facts from facter -p, similar to facter_task. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-1952) Run specs against jruby
Title: Message Title Craig Gomes assigned an issue to Jacob Helwig Puppet / PUP-1952 Run specs against jruby Change By: Craig Gomes Assignee: Eric Delaney 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-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Craig Gomes assigned an issue to Jacob Helwig Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Craig Gomes Assignee: Eric Delaney 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-8514) Puppet should have a way of defining properties or parameters for types as sensitive
Title: Message Title Craig Gomes assigned an issue to Jorie Tappa Puppet / PUP-8514 Puppet should have a way of defining properties or parameters for types as sensitive Change By: Craig Gomes Assignee: Jorie Tappa 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-8421) Add error handing to Yum provider
Title: Message Title Craig Gomes assigned an issue to Jorie Tappa Puppet / PUP-8421 Add error handing to Yum provider Change By: Craig Gomes Assignee: Jorie Tappa 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-7307) Tidy should support 'purge' or update file resource
Title: Message Title Craig Gomes assigned an issue to Jacob Helwig Puppet / PUP-7307 Tidy should support 'purge' or update file resource Change By: Craig Gomes 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-4678) Enable yumrepo priority attribute to support lower priority than 99
Title: Message Title Craig Gomes assigned an issue to Melissa Stone Puppet / PUP-4678 Enable yumrepo priority attribute to support lower priority than 99 Change By: Craig Gomes Assignee: Melissa Stone 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-8556) environment.conf modulepath should accept globs
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8556 environment.conf modulepath should accept globs Change By: Melissa Stone 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-7534) Deprecate using file checksums in `content` property
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7534 Deprecate using file checksums in `content` property Change By: Kenn Hussey Flagged: Impediment 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-8619) File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8619 File Resource: error when attempting to use checksum and checksum_value to retrieve from filebucket Change By: Kenn Hussey Flagged: Impediment 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 (PDB-3874) (maint) update clj-parent and rbac dependencies
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3874 (maint) update clj-parent and rbac dependencies Change By: Kenn Hussey Flagged: Impediment 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-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Kenn Hussey Flagged: Impediment 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 (PDB-3874) (maint) update clj-parent and rbac dependencies
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3874 (maint) update clj-parent and rbac dependencies Change By: Kenn Hussey Team: Data Platform 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 (PDB-3862) replace facts failing for some nodes
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Kenn Hussey Flagged: Impediment 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 (PDB-3856) PQL specifying both type and title for class makes pql not find existing class
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3856 PQL specifying both type and title for class makes pql not find existing class Change By: Kenn Hussey Flagged: Impediment 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 (PDB-3852) PuppetDB query nodes based on fact broken
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3852 PuppetDB query nodes based on fact broken Change By: Kenn Hussey Flagged: Impediment 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 (PDB-3878) Remove Debian 7 (i386, amd64) from puppetdb pipelines
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3878 Remove Debian 7 (i386, amd64) from puppetdb pipelines Change By: Kenn Hussey Fix Version/s: PDB 5.2.2 Fix Version/s: PDB 5.2.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 (PDB-3900) Check builds, promote to PE (PuppetDB 5.2.2)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3900 Check builds, promote to PE (PuppetDB 5.2.2) Change By: Kenn Hussey Due Date: 2018/04/ 14 13 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 (PDB-3894) Check builds, promote to PE (PuppetDB 5.1.5)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3894 Check builds, promote to PE (PuppetDB 5.1.5) Change By: Kenn Hussey Due Date: 2018/04/ 14 13 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 (PDB-3900) Check builds, promote to PE (PuppetDB 5.2.2)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3900 Check builds, promote to PE (PuppetDB 5.2.2) Issue Type: Task Assignee: Zachary Kent Created: 2018/04/09 7:01 AM Due Date: 2018/04/14 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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. Adding a new tab to Jenkins: If needed hit the + tab in the link above, select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.x
Jira (PDB-3899) Bump versions, push directly, and tag (PuppetDB 5.2.2)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3899 Bump versions, push directly, and tag (PuppetDB 5.2.2) Issue Type: Task Assignee: Zachary Kent Created: 2018/04/09 7:01 AM Due Date: 2018/04/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) (if you're making the first release off a new branch you may already have done some of this) Remove the -SNASPHOT portion of the verison in project.clj in both puppetdb and pe-puppetdb-extensions. Push each repo directly to the branch you're releasing (making a PR will break things horribly) Go into the 'release-new' hipchat room to make yourself some tags ! tag puppetdb at with ! tag pe-puppetdb-extensions at with
Jira (PDB-3901) Update winston (PuppetDB 5.2.2)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3901 Update winston (PuppetDB 5.2.2) Issue Type: Task Assignee: Zachary Kent Created: 2018/04/09 7:01 AM Due Date: 2018/04/18 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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 (PDB-3897) Merge-up, branch, and create pipelines (PuppetDB 5.2.2)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-3897
Merge-up, branch, and create pipelines (PuppetDB 5.2.2)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2018/04/09 7:01 AM
Due Date:
2018/04/10
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2018-04-17) 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
5.1.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.1.x/
4.4.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.4.x/
4.2.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.2.3.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PDB-3898) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.2)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3898 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.2) Issue Type: Task Assignee: Zachary Kent Created: 2018/04/09 7:01 AM Due Date: 2018/04/10 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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 (PUP-8647) Update Confluence and JIRA based on release (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8647 Update Confluence and JIRA based on release (Puppet Platform 5.5.1) Issue Type: Task Assignee: Kenn Hussey Created: 2018/04/09 7:00 AM Due Date: 2018/04/18 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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 description
Jira (PUP-8648) Communicate scope and timeline of next release (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8648 Communicate scope and timeline of next release (Puppet Platform 5.5.1) Issue Type: Task Assignee: Kenn Hussey Created: 2018/04/09 7:00 AM Due Date: 2018/04/18 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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-8645) Prepare release announcement (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8645 Prepare release announcement (Puppet Platform 5.5.1) Issue Type: Task Assignee: Garrett Guillotte Created: 2018/04/09 6:59 AM Due Date: 2018/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) Please paste the text of the announcement in the 'Send announcement' ticket. 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-8642) Puppet Platform 5.5.1 Release - 2018-04-17
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8642 Puppet Platform 5.5.1 Release - 2018-04-17 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/04/09 6:59 AM Due Date: 2018/04/17 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.1 Release - 2018-04-17 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8644) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8644 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.1) Issue Type: Task Assignee: Kenn Hussey Created: 2018/04/09 6:59 AM Due Date: 2018/04/11 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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-8643) Prepare JIRA for release (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8643 Prepare JIRA for release (Puppet Platform 5.5.1) Issue Type: Task Assignee: Kenn Hussey Created: 2018/04/09 6:59 AM Due Date: 2018/04/11 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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) 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. 3) 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. 4) Update the “master” filters for Puppet Platform 5.5.1 and puppet-agent 5.5.1 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.
Jira (PUP-8646) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.1)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8646 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.1) Issue Type: Task Assignee: Kenn Hussey Created: 2018/04/09 6:59 AM Due Date: 2018/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-04-17) 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-2076) Unit Tests Fail if not run as root (continues http://projects.puppetlabs.com/issues/16248)
Title: Message Title
Chadwick commented on PUP-2076
Re: Unit Tests Fail if not run as root (continues http://projects.puppetlabs.com/issues/16248)
Just an FYI – it looks like a mocha update from 1.4.0 to 1.5.0 makes this workaround blow up with the following error: Failure/Error: Puppet.features.stubs(:root? => true) {{ Mocha::NotInitializedError:}} {{ Mocha methods cannot be used outside the context of a test}}
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-8641) Make call() function resolve Deferred values
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8641 Make call() function resolve Deferred values Issue Type: New Feature Assignee: Henrik Lindberg Components: Language, Type System Created: 2018/04/09 12:43 AM Fix Versions: PUP 5.y Priority: Normal Reporter: Henrik Lindberg While the primary use of a Deferred is to defer the evaluation to catalog apply time it is very useful to also be able to resolve values when compiling: For the purpose of testing Deferred values To delay the evaluation of an expensive function until it is actually needed To delay a reference to a variable that may not yet exist The same can be achieved without Deferred by instead of creating a Deferred the information would be encoded in a hash or array, and the receiver making a call to call or other functions (typically an ERB template) to get a variable value via indirect name reference. See PUP-8635 for the Deferred data type.
