Jira (FACT-380) Private ipaddress is used as ipaddress fact
Title: Message Title Roger Ignazio commented on FACT-380 Re: Private ipaddress is used as ipaddress fact I was talking to Branan Riley about this today and we want to consider improving this logic for Facter 3. As several people have stated above, it seems sane to use the default route to determine the interface used to populate the ipaddress fact. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3196) windows ruby 2.0 x64 segfault in specs
Title: Message Title Roger Ignazio commented on PUP-3196 Re: windows ruby 2.0 x64 segfault in specs The Rubies available on Windows spec boxes are all from RubyInstaller.org and loaded via Pik. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-154) Add hiera spec windows jobs
Title: Message Title Roger Ignazio commented on HI-154 Re: Add hiera spec windows jobs Justin Stoller - Will the AIO testing jobs include running Hiera specs on Windows? If so, can I close this ticket? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3378) False positives in Puppet acceptance testing - should_not_change_the_system.rb
Title: Message Title Roger Ignazio commented on PUP-3378 Re: False positives in Puppet acceptance testing - should_not_change_the_system.rb Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Roger Ignazio commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 Saw this ticket was closed, has this new configuration been added to our Puppet Solaris acceptance job(s) in Jenkins? Or is there a separate ticket where I should do that? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Roger Ignazio commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 If someone could ping me when this is complete, I can add solaris10 into Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2366) Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Puppet / PUP-2366 Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2366) Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance
Title: Message Title Roger Ignazio commented on PUP-2366 Re: Replace hosts using Ruby 1.8.7 for Puppet 4.0 Acceptance Removed rhel6, rhel5, centos5, lucid, precise, precise_and_lucid, and squeeze platforms from Puppet Package Acceptance, master branch. Also removed RHEL 6 from Puppet Acceptance Future Parser, master branch. PR opened (see links above) against Puppet master to bump the masters for Windows testing from EL 6 to EL 7. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3272) Remove support for yaml on the network
Title: Message Title Roger Ignazio commented on PUP-3272 Re: Remove support for yaml on the network This PR has failed CI, specifically with the removal of ext/puppet-load.rb. I have another PR up (https://github.com/puppetlabs/puppet/pull/3288) that removes ext/puppet-load.rb from ext/redhat/puppet.spec.erb, which should resolve the packaging failures and allow acceptance testing to proceed. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Roger Ignazio commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 It appears our Solaris acceptance jobs only test against Solaris 11. I don't have anything in the backlog for Solaris 10. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-154) Add hiera spec windows jobs
Title: Message Title Roger Ignazio commented on an issue Re: Add hiera spec windows jobs Hey Josh Cooper - there were a few other tickets for running Hiera acceptance on Windows. Off the top of my head I don't think this is a dupe. I think this may be related to QA-682? Add Comment Hiera / HI-154 Add hiera spec windows jobs Not sure if this belongs in QA or HI, but we are not currently running hiera specs on windows. We need to add jobs for stable and master against ci-win2003 and ci-win2008r2. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2015) Identify and fix test slowdowns on windows
Title: Message Title Roger Ignazio commented on an issue Re: Identify and fix test slowdowns on windows Hey Rob Reynolds - Even with our rebuilt Jenkins environment in the new datacenter, we're still seeing Windows 2003 specs take longer than the other Windows releases (but that isn't anything new). Here are the latest test durations for Puppet, stable branch, running specs on Windows: label=unit-win2012,ruby=ruby-1.9.3-p484 9 min 37 sec label=unit-win2003,ruby=ruby-1.9.3-p484 26 min label=unit-win2008,ruby=ruby-1.9.3-p484 8 min 31 sec label=unit-win2008,ruby=ruby-2.0.0-p481 8 min 17 sec label=unit-win2012,ruby=ruby-2.0.0-p481 9 min 6 sec The historical test times / graphs are looking much more consistent, which I believe was the original intent of this ticket. Here are a few examples: https://jenkins.puppetlabs.com/job/Puppet-Specs-Windows-stable/lastCompletedBuild/label=unit-win2003,ruby=ruby-1.9.3-p484/testReport/(root)/history/ https://jenkins.puppetlabs.com/job/Puppet-Specs-Windows-stable/lastCompletedBuild/label=unit-win2008,ruby=ruby-1.9.3-p484/testReport/(root)/history/ https://jenkins.puppetlabs.com/job/Puppet-Specs-Windows-stable/lastCompletedBuild/label=unit-win2012,ruby=ruby-2.0.0-p481/testReport/(root)/history/
Jira (PUP-3378) False positives in Puppet acceptance testing - should_not_change_the_system.rb
Title: Message Title Roger Ignazio created an issue Puppet / PUP-3378 False positives in Puppet acceptance testing - should_not_change_the_system.rb Issue Type: Bug Assignee: Unassigned Created: 01/Oct/14 8:46 AM Priority: Normal Reporter: Roger Ignazio When running the Puppet acceptance suite, we're seeing some flakiness in acceptance/tests/resource/service/should_not_change_the_system.rb. This doesn't appear to be a problem with Puppet, but rather a problem with the test. The test runs puppet resource service twice and compares the output. On Fedora 19, we're seeing the NetworkManager service changes state in between. It is not immediately apparent what causes this service's state to change. Ideally, we need to modify this test to be less fragile, and more directly test puppet resource service. Add Comment
Jira (PDB-121) Add Ruby 2.0.0 to spec test matrix for puppetdb
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio PuppetDB / PDB-121 Add Ruby 2.0.0 to spec test matrix for puppetdb Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-252) Spec jobs should run from an artifact of checked out code rather than each one hitting Github.
Title: Message Title Roger Ignazio commented on an issue Re: Spec jobs should run from an artifact of checked out code rather than each one hitting Github. Hey Joshua Partlow - I believe the desired effect has been achieved. Instead of packaging the checkout into a tarball and storing that somewhere for some amount of time, the new specs kick-off jobs pass build parameters and the Git SHA retrieved from the parent job to all the subprojects. So we can be sure the same commit is being built in all of our parallelized spec jobs, without the need to create an artifact. From the Jenkins Git plugin: This parameter passes the SHA1 commit ID that was built by this project into the specified job, and thereby causes the specified job to check out the exact same commit. This is useful to chain multiple activities in a sequence that acts on the same commit in different ways Take a look at the Build section of https://jenkins.puppetlabs.com/view/Facter/view/Master/job/Facter-Pipeline-Kickoff-master/configure if you'd like to see this in practice Add Comment Puppet / PUP-252 Spec jobs should run from an artifact of checked out code rather than each one hitting Github. So, probably github should point to a jenkin's job that tar's up a single checkout, saves it as an artifact and flicks the first spec matrix job, which uses the artifact to run the tests (and then cascades on to solaris, windows...assuming those still need to be separate because of different script requirements).
Jira (PUP-587) Update windows acceptance jobs to install from MSI packages
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Puppet / PUP-587 Update windows acceptance jobs to install from MSI packages Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-8) Hiera stable acceptance testing for Windows using VCloud
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-8 Hiera stable acceptance testing for Windows using VCloud Change By: Roger Ignazio Assignee: MichelleJohansen RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-9) Hiera stable acceptance testing for Solaris with Vcloud
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-9 Hiera stable acceptance testing for Solaris with Vcloud Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-7) Hiera stable acceptance tests use dynamically provisioned vcloud templates.
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Hiera / HI-7 Hiera stable acceptance tests use dynamically provisioned vcloud templates. Change By: Roger Ignazio Assignee: JoshuaPartlow RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2982) Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Puppet / PUP-2982 Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2 Change By: Roger Ignazio Assignee: RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2982) Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2
Title: Message Title Roger Ignazio commented on an issue Re: Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2 Windows full-matrix 'stable' acceptance job has been reconfigured to match 'master'. Still need to re-work the per-commit jobs. Add Comment Puppet / PUP-2982 Reconfigure Jenkins jobs for Puppet Windows acceptance on stable for Ruby 2 Changes are presently only in master jobs, but will need to be carried over to other jobs once changes have been merged into other branches: https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Acceptance-Windows-Per-Commit-master/ https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/job/Puppet-Acceptance-Windows-master-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3102) Merge master into stable
Title: Message Title
Roger Ignazio commented on an issue
Re: Merge master into stable
Kylo Ginsberg - that's correct. Instead of ... junit/.xml we would need to modify them to ... junit/latest/.xml.
Do we have a schedule for this? If we need to do it before Thursday, we'll need to update the new Jenkins environment configs as well.
Add Comment
Puppet / PUP-3102
Merge master into stable
For some releases, the code base will need to be merged down to stable. *NOTE:* This is usually only during a x.y.0-rc1 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: {noformat} git fetch up...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-2949) Enable rubocop verification in Jenkins
Title: Message Title Roger Ignazio assigned an issue to Roger Ignazio Puppet / PUP-2949 Enable rubocop verification in Jenkins Change By: Roger Ignazio Assignee: RahulGopinath RogerIgnazio Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2949) Enable rubocop verification in Jenkins
Title: Message Title Roger Ignazio commented on an issue Re: Enable rubocop verification in Jenkins Kylo Ginsberg: do you have any qualms about me moving this to the QENG tracker so I can schedule it in our next sprint? Add Comment Puppet / PUP-2949 Enable rubocop verification in Jenkins Once PUP-2909 is complete, we should integrate rubocop task to Jenkins This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio updated an issue Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. Change By: Roger Ignazio Assignee: QA JoshuaPartlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Kylo Ginsberg it looks like 'Failed Test' in your workflow automatically assigns to QA. I re-assigned to Joshua Partlow since he was working on this fixes for this. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title
Roger Ignazio commented on an issue
Re: Run Facter acceptance against ruby 2.0 x64
The Win2003 x64 cells have been disabled per the combo filter: !(platform =~ /win2003/ ruby_arch =~ /x64/)
If and when we're ready to re-enable them, modify the combo filter to be: !(platform =~ /x86/ ruby_arch =~ /x64/)
Add Comment
Facter / FACT-569
Run Facter acceptance against ruby 2.0 x64
Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's {{install_from_git}} method accepts a {{:rev}} parameter so it should be possible to specify the revision to checkout, e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title
Roger Ignazio commented on an issue
Re: Run Facter acceptance against ruby 2.0 x64
Rob Reynolds - Facter PR 733 is ready for review.
Add Comment
Facter / FACT-569
Run Facter acceptance against ruby 2.0 x64
Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's {{install_from_git}} method accepts a {{:rev}} parameter so it should be possible to specify the revision to checkout, e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title
Roger Ignazio commented on an issue
Re: Run Facter acceptance against ruby 2.0 x64
Jenkins jobs have been reconfigured and have run against the new nodesets.
Rob Reynolds and Josh Cooper - I think that concludes the scope of this ticket. We have known issues with Ruby 2.0 x64 running on Windows 2003. I'll move this ticket into Ready for Review and let one of you decide if it's ready to be closed.
Add Comment
Facter / FACT-569
Run Facter acceptance against ruby 2.0 x64
Facter's acceptance setup step for git will need to install the appropriate version of ruby based on the agent's architecture. See https://github.com/puppetlabs/facter/blob/facter-2/acceptance/setup/common/00_EnvSetup.rb#L37 Beaker's {{install_from_git}} method accepts a {{:rev}} parameter so it should be possible to specify the revision to checkout, e...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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
Jira (PUP-417) Add acceptance cells which test with passenger instead of webrick.
Title: Message Title Roger Ignazio commented on an issue Re: Add acceptance cells which test with passenger instead of webrick. Joshua Partlow - ready for merge is fine. I've created QENG-956 for the Beaker 1.16 release and added it as a blocker to this ticket. Once that's resolved, we can merge PR 2871. Add Comment Puppet / PUP-417 Add acceptance cells which test with passenger instead of webrick. One way to do this is to install puppetmaster-passenger on Debian platforms. However if we want both webrick and passenger coverage on Debian, then it's not as simple as modifying the packages setup process. There is conversation about this in the 9/25 Hipchat logs around 11AM, re webrick and passenger. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2414) Get Puppet acceptance to use the new internal forge being set up by the module team.
Title: Message Title Roger Ignazio commented on an issue Re: Get Puppet acceptance to use the new internal forge being set up by the module team. Based on discussions with Dominic Maraglia and Justin Stoller, this ticket should be moved to the QENG tracker so that it can be triaged and moved into a future QENG sprint. This way I'm not straddling two sprints every week/two weeks. Add Comment Puppet / PUP-2414 Get Puppet acceptance to use the new internal forge being set up by the module team. Currently Puppet Acceptance relies on being able to reach a testing forge instance forge-aio01-petest.puppetlabs.com. This is an external node hosted on linode, and susceptible to all the same connectivity issues which have caused us to create local rubygem, github and packaging mirrors. So a request was put in for an internal forge instance for testing... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2406) Run all acceptance jobs in parallel
Title: Message Title Roger Ignazio commented on an issue Re: Run all acceptance jobs in parallel Based on discussions with Dominic Maraglia and Justin Stoller, this ticket should be moved to the QENG tracker so that it can be triaged and moved into a future QENG sprint. This way I'm not straddling two sprints every week/two weeks. Add Comment Puppet / PUP-2406 Run all acceptance jobs in parallel Right now it takes up to 4 or 5 hours from the start of a test pipeline run to the end. We should be able to reduce this by an hour if we start the linux, solaris, and windows acceptance jobs all at the same time instead of gating the Windows and Solaris jobs on a good Linux run. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
