Jira (FACT-1940) Investigate Facter 2.x
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1940 Investigate Facter 2.x Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:02 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-1941) Investigate C++ facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1941 Investigate C++ facter Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:03 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-1942) Investigate Ohai
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1942 Investigate Ohai Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:04 AM Priority: Normal Reporter: Bogdan Irimie 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.
Jira (FACT-1944) Investigate custom facts
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1944 Investigate custom facts Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:06 AM Priority: Normal Reporter: Bogdan Irimie 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/pupp
Jira (FACT-1945) Create new repo for Facter NG
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1945 Create new repo for Facter NG Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:06 AM Priority: Normal Reporter: Bogdan Irimie 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
Jira (FACT-1943) Investigate Ansible facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1943 Investigate Ansible facter Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:05 AM Priority: Normal Reporter: Bogdan Irimie 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/pu
Jira (FACT-1946) Investigate ffi shipment/packaging (does it need compilation on target system?)
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1946 Investigate ffi shipment/packaging (does it need compilation on target system?) Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:07 AM Priority: Normal Reporter: Bogdan Irimie 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. V
Jira (FACT-1947) Investigate and migrate acceptance tests from old c++ facter into new ruby facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1947 Investigate and migrate acceptance tests from old c++ facter into new ruby facter Issue Type: Epic Assignee: Unassigned Created: 2019/07/17 5:09 AM Priority: Normal Reporter: Bogdan Irimie 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.
Jira (FACT-1949) Move acceptance tests in new facter respo
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1949 Move acceptance tests in new facter respo Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:12 AM Priority: Normal Reporter: Bogdan Irimie 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.goog
Jira (FACT-1948) Investigate acceptance tests from C++ facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1948 Investigate acceptance tests from C++ facter Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:10 AM Priority: Normal Reporter: Bogdan Irimie 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.g
Jira (FACT-1950) Create Jenkins pipeline for acceptance tests
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1950 Create Jenkins pipeline for acceptance tests Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:13 AM Priority: Normal Reporter: Bogdan Irimie 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.g
Jira (FACT-1951) Create the git repo, configure travis
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1951 Create the git repo, configure travis Issue Type: Epic Assignee: Unassigned Created: 2019/07/17 5:14 AM Priority: Normal Reporter: Bogdan Irimie 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.c
Jira (FACT-1955) Create CLi compatible with the one from C++ facter.
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1955 Create CLi compatible with the one from C++ facter. Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:19 AM Priority: Normal Reporter: Bogdan Irimie 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://g
Jira (FACT-1954) Integrate code coverage into facter project
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1954 Integrate code coverage into facter project Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:17 AM Priority: Normal Reporter: Bogdan Irimie 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.go
Jira (FACT-1952) Configure Travis to run unit tests
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1952 Configure Travis to run unit tests Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:16 AM Priority: Normal Reporter: Bogdan Irimie 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/
Jira (FACT-1953) Investigate code coverage tools
Title: Message Title Bogdan Irimie created an issue Facter / FACT-1953 Investigate code coverage tools Issue Type: Task Assignee: Unassigned Created: 2019/07/17 5:17 AM Priority: Normal Reporter: Bogdan Irimie 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/gro
Jira (FACT-1940) Investigate Facter 2.x
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1940 Investigate Facter 2.x Change By: Bogdan Irimie Code can be found at:[https://github.com/puppetlabs/facter/tree/2.x] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316804.156336494.19246.1563366600108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1941) Investigate C++ facter
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1941 Investigate C++ facter Change By: Bogdan Irimie Code can be found at:[https://github.com/puppetlabs/facter/tree/master] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316805.1563365003000.19247.1563366600156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1942) Investigate Ohai
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1942 Investigate Ohai Change By: Bogdan Irimie Code can be found at:[https://github.com/chef/ohai] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316806.156336507.19248.156330087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1943) Investigate Ansible facter
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1943 Investigate Ansible facter Change By: Bogdan Irimie Code can be found at:https://github.com/ansible/ansible/tree/devel/lib/ansible/module_utils/facts 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316807.1563365115000.19249.156330091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1948) Investigate acceptance tests from C++ facter
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1948 Investigate acceptance tests from C++ facter Change By: Bogdan Irimie Code can be found at:[https://github.com/puppetlabs/facter/tree/master/acceptance] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316812.1563365421000.19250.1563366720065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1949) Move acceptance tests in new facter respo
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1949 Move acceptance tests in new facter respo Change By: Bogdan Irimie Move tests from:[https://github.com/puppetlabs/facter/tree/master/acceptance]to new repo. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316813.1563365552000.19251.1563367080058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1938) Create benchmark tool
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-1938
Create benchmark tool
Change By:
Bogdan Irimie
Config file example (json format){code:java}[ "TestRun1": {"facts": [ "f1": 3 "f2": 5 "f3,f4": 10] }]{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316642.1563283827000.19346.1563375120219%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1938) Create benchmark tool
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-1938
Create benchmark tool
Change By:
Bogdan Irimie
Config file example (json format){code:java}[ "TestRun1": {"facts": [ "f1": 3 "f2": 5 "f3,f4": 10] }, "TestRun2": {... }]{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316642.1563283827000.19352.1563375180342%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1938) Create benchmark tool
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-1938
Create benchmark tool
Change By:
Bogdan Irimie
Config file example (json format){code:java}[ "TestRun1": {"facts": [ "f1": 3 "f2": 5 "f3,f4": 10] }, "TestRun2": {... }]{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316642.1563283827000.19354.1563375180353%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1938) Create benchmark tool
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-1938
Create benchmark tool
Change By:
Bogdan Irimie
Config file example (json format){code:java} [ "TestRun1": {"facts": [ "f1": 3 "f2": 5 "f3,f4": 10] } , "TestRun2": {... } ]{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316642.1563283827000.19350.1563375180334%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1472) Automated Test WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet Task Runner / BOLT-1472 Automated Test WinRM with Kerberos (from Linux node) Change By: Ethan Brown Assignee: Ethan Brown 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316522.1563208774000.19611.1563381240142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1472) Automated Test WinRM with Kerberos (from Linux node)
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-1472 Automated Test WinRM with Kerberos (from Linux node) Change By: Ethan Brown 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316522.1563208774000.19612.1563381300071%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1956) EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1
Title: Message Title Sean Kumar created an issue Facter / FACT-1956 EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1 Issue Type: Bug Assignee: Unassigned Components: CLI, Community Created: 2019/07/17 9:47 AM Environment: Linux ip-10-3-2-218 4.9.70-25.242.amzn1.x86_64 #1 SMP Wed Jan 3 05:36:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Priority: Critical Reporter: Sean Kumar Facter at version 2.5.4 can no longer read and display facts from EC2 Metadata in AWS. Facter @ 2.5.4 [root@ip-10-3-2-87 log]# facter | grep ec2 serialnumber => ec23a2bd-0a32-7111-8ee9-ecd6038d22d0 Facter @ 2.5.1 [root@ip-10-3-2-85 vkumase]# facter | grep ec2
Jira (FACT-1956) EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1
Title: Message Title Sean Kumar updated an issue Facter / FACT-1956 EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1 Change By: Sean Kumar Method Found: Needs Assessment Other (please specify in description) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316838.1563382036000.19656.1563382200445%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1956) EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1
Title: Message Title
Sean Kumar updated an issue
Facter / FACT-1956
EC2 Metadata Broken with Facter 2.5.4 - Works Fine in 2.5.1
Change By:
Sean Kumar
Facter at version 2.5.4 can no longer read and display facts from EC2 Metadata in AWS. This has been breaking our puppet runs across Puppet and Dev environments, as on bootstrap we're automatically pulling the latest in the 2.x series. Facter @ 2.5.4{code:java} [root@ip-10-3-2-87 log]# facter | grep ec2serialnumber => ec23a2bd-0a32-7111-8ee9-ecd6038d22d0{code}Facter @ 2.5.1{code:java} [root@ip-10-3-2-85 vkumase]# facter | grep ec2domain => ec2.internalec2_ami_id => ami-923b64e8ec2_ami_launch_index => 0ec2_ami_manifest_path => (unknown)ec2_block_device_mapping_ami => /dev/xvdaec2_block_device_mapping_ebs1 => xvdczec2_block_device_mapping_root => /dev/xvdaec2_events_maintenance_history => []ec2_events_maintenance_scheduled => []ec2_hostname => ip-10-3-2-85ec2_iam_info_0 => {ec2_iam_info_1 => "Code" : "Success",ec2_iam_info_2 => "LastUpdated" : "2019-07-17T15:54:48Z",{code}This will break all Puppet modules that are using EC2 metadata as a fact in older puppet installations.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1400) Add 'run_command' endpoint to bolt-server
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-1400 Add 'run_command' endpoint to bolt-server Change By: Geoff Nichols Sprint: Skeletor Kanban 20190619, Skeletor Kanban 20190703, Skeletor Kanban 20190717 , Skeletor Kanban 20190731 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312869.1560800327000.19844.1563387182686%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title Geoff Nichols updated an issue Puppet Task Runner / BOLT-1468 implement wait_until_available in bolt-server Change By: Geoff Nichols Sprint: Skeletor Kanban 20190717 , Skeletor Kanban 20190731 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.19869.1563387182803%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Josh Cooper commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist It would be very surprising if an agent automatically switched to production if the $codedir/environments/ directory didn't exist, as we couldn't differentiate between the scenario you're describing and simple misconfiguration (set the branch and forgot to checkout the branch). I think you're better off keeping the logic for checking out/deleting branches and setting/unsetting the agent environment in the same agent-side code that runs puppet. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.232102.1516564527000.19933.1563388320164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-8376 Revert to production when agent-specified environment doesn't exist 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.232102.1516564527000.19941.1563388380237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9249) Backport sensitive DSL method PUP-8514
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9249
Backport sensitive DSL method PUP-8514
Change By:
Josh Cooper
Acceptance Criteria:
Should have the same behavior as the 6.0.0+ versions. Install 1.0.1 yumrepo_core on the masterAdd yumrepo resource:{code:puppet}yumrepo { 'puppetrepo-products': ensure=> 'present', name => 'puppetrepo-products', password => 'password', descr => 'Puppet Labs Products El 7 - $basearch', baseurl => 'http://myownmirror', gpgkey=> 'http://myownmirror', enabled => '1', gpgcheck => '1', target=> '/etc/yum.repo.d/puppetlabs.repo',}{code}Run redhat/centos agentMake sure yumrepo resource is created in /etc/yumMake sure password is set correctly in the repo config, and is not written to the console (even at debug level)
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.
To view this disc
Jira (PUP-9249) Backport sensitive DSL method PUP-8514
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Change By: Josh Cooper Fix Version/s: PUP 6.0.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281329.1539907632000.20180.1563396480196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9829) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9829 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9832) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9832 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 2:22 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9830) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9830 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9833) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9833 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9831) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9831 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:22 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9828) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9828 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 2:22 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9835) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9835 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 2:23 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9834) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9834 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:23 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9836) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9836 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:23 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9837) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9837 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:24 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9838) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9838 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9842) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9842 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 2:29 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9840) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9840 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9841) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9841 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:29 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9843) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9843 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9839) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9839 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:29 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9846) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9846 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:30 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9845) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9845 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 2:30 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9844) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9844 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 2:30 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9847) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9847 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 2:31 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 (PDB-4323) Update explicit lifetime node behavior in PDB
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4323 Update explicit lifetime node behavior in PDB Change By: Rob Browning Summary: Updating Update explicit lifetime node behavior in PDB 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302291.1553880231000.20362.1563399540544%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9848) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9848 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9851) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9851 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:32 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9849) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9849 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9850) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9850 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:32 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9854) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9854 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:33 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9852) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9852 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 3:33 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9853) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9853 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:33 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9857) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9857 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:34 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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-9855) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9855 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 3:34 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9856) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9856 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:34 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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 d
Jira (PUP-9858) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Molly Waggett created an issue Puppet / PUP-9858 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 3:39 PM Due Date: 2019/07/23 Priority: Normal Reporter: Molly Waggett Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9861) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9861 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:39 PM Due Date: 2019/07/19 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9859) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9859 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:39 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to ref
Jira (PUP-9864) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9864 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:39 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9860) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9860 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:39 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9863) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9863 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:39 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9862) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9862 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 3:39 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9865) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9865 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 3:40 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9866) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9866 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:40 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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 descr
Jira (PUP-9867) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9867 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:40 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9858) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Molly Waggett commented on PUP-9858 Re: Puppet Platform 6.7.0 Release - 2019-07-23 closing all these because winston bailed in the middle 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316941.1563403143000.20603.1563403740088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9870) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9870 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:55 PM Due Date: 2019/07/18 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9868) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Molly Waggett created an issue Puppet / PUP-9868 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 3:55 PM Due Date: 2019/07/23 Priority: Normal Reporter: Molly Waggett Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9871) Prepare documentation updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9871 Prepare documentation updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:55 PM Due Date: 2019/07/20 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9869) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9869 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:55 PM Due Date: 2019/07/18 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to ref
Jira (PUP-9872) Prepare release announcement (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9872 Prepare release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Bill Tang Created: 2019/07/17 3:56 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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-9873) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9873 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:56 PM Due Date: 2019/07/22 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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 ‘Proj-puppet-releases’ Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9874) Publish documentation and updates and release notes (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9874 Publish documentation and updates and release notes (Puppet Platform 6.7.0) Issue Type: Task Assignee: Jean Bond Created: 2019/07/17 3:56 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9875) Send release announcement (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9875 Send release announcement (Puppet Platform 6.7.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2019/07/17 3:57 PM Due Date: 2019/07/23 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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.7.0 is now available".
Jira (PUP-9876) Update Confluence and JIRA based on release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9876 Update Confluence and JIRA based on release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:57 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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 descr
Jira (PUP-9877) Communicate scope and timeline of next release (Puppet Platform 6.7.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-9877 Communicate scope and timeline of next release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 3:57 PM Due Date: 2019/07/24 Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2019-07-23) 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 (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Kami Olszewski commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Geoff Nichols and David Kramer what is the timeline to expect these changes to the documented instruction to be implemented? My understanding is this was requested months ago and we believe this should be made public asap so other customers do not run into this. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20716.1563404700311%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title
Molly Waggett updated an issue
Puppet Task Runner / BOLT-1300
Update install docs to point to puppet-tools repo
Change By:
Molly Waggett
We now have a {{puppet- enterprise- tools}} repo on {yum,apt}.puppet.com that can be used to install Bolt safely without interfering with the {{puppet-agent}} package on a PE-managed node. We currently have a note warning PE users not to setup the repo and to install the packages individually. That workflow means they can't easily upgrade their version of bolt, but it's necessary to avoid accidentally clobbering their puppet-agent with a newer version.Now that we have the {{puppet- enterprise- tools}} repo, we can refer PE users to that, so they can get the same benefits of having updates easily available through their package manager.
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 receivi
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Molly Waggett updated an issue Puppet Task Runner / BOLT-1300 Update install docs to point to puppet-tools repo Change By: Molly Waggett Summary: Update install docs to point to puppet- enterprise- tools repo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20752.1563405180808%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo I have puppet-tools packages ready to ship as soon as I get confirmation (perhaps from Jean Bond?) that any existing docs pointing to puppet-enterprise-tools are ready to be changed to puppet-tools. Nick Walker Garrett Guillotte I'd also love to know if you've already told people about the puppet-enterprise-tools repo. because, if so, you'll need to let them know that it's changing to puppet-tools (though we intend to maintain compatibility with puppet-enterprise-tools for the moment). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20789.1563405600521%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9868) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Molly Waggett commented on PUP-9868 Re: Puppet Platform 6.7.0 Release - 2019-07-23 closing all these because winston bailed in the middle 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.316956.1563404141000.20803.1563405720068%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Nick Walker commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo I haven't told anyone about it. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20862.1563407340435%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Garrett Guillotte commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo Molly Waggett Per my questions on PE-26104, I was waiting for confirmation about the Bolt docs update before informing customers of a Bolt installation process update, and I was referred to this ticket. I haven't pointed anyone to the PDK doc to resolve the Bolt installation docs discrepancy because that doc does not provide a solution, and after a quick search of support cases I don't see any references to that repo or the PDK docs in question. My primary concerns haven't changed since April on PE-26104: the Bolt installation docs are dangerous to PE users, some PE customers are navigating past the warning on the page and following the dangerous docs, some customers who do read the warning don't understand the severity of the risks that it suggests and follow the dangerous docs, safe installation docs for Bolt on PE nodes do not exist, and PE docs that reference Bolt installation link to the unsafe docs. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20889.1563407640304%40Atlassian.JIRA. For more options, visit https://groups.google.com/
Jira (BOLT-1300) Update install docs to point to puppet-tools repo
Title: Message Title Molly Waggett commented on BOLT-1300 Re: Update install docs to point to puppet-tools repo okay, I will ship the puppet-tools release packages tomorrow and then it's just docs changes. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.20917.1563408000446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9879) Prepare JIRA and Confluence for release (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9879 Prepare JIRA and Confluence for release (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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.7.0 and puppet-agent 6.7.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9878) Puppet Platform 6.7.0 Release - 2019-07-23
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9878 Puppet Platform 6.7.0 Release - 2019-07-23 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/23 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.7.0 Release - 2019-07-23 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9880) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9880 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.7.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/07/17 6:18 PM Due Date: 2019/07/17 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-07-23) 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
