On Monday, August 8, 2016 at 8:30:27 PM UTC-7, Garrett Honeycutt wrote: > > On 8/5/16 9:12 PM, Geoff Nichols wrote: > > > > > > On Friday, July 29, 2016 at 5:00:26 PM UTC-7, Geoff Nichols wrote: > > > > Because Ruby 2.1 is approaching end-of-life (upstream bugfix support > > ended March 2016), we need to move puppet-agent to a more modern > > Ruby version. > > > > > > If all goes well with testing, the upcoming puppet-agent 1.6.0 > > release will include Ruby 2.3.1. > > > > > > As an update, we found some issues during testing, so puppet-agent 1.6.0 > > will NOT include Ruby 2.3.1. > > > > We're now targeting the Ruby 2.3 update for a later puppet-agent > > release. (We'll share more information about that timeframe as the plan > > firms up.) > > > > Thanks, > > Geoff > > > > Hi Geoff, > > It seems that the testing is leaving out the huge dataset of modules > from the Forge. Checked out the TravisCI configs for a couple of the top > supported modules including stdlib, apache, ntp, apt and vcsrepo and > none of them are testing with ruby 2.3. Suggest that before moving to a > new version of ruby, the TravisCI configs for all supported modules > should be explicitly testing against the new ruby version to ensure it > works. >
We have tested on some Windows modules with success. Generally speaking, I believe we're more likely to see issues in modules that have Ruby type and provider code than we are in modules that are primarily manifest driven. That said, I totally agree we should get module testing changes rolled out officially ASAP. For the Windows modules, we'll plan on getting all the Travis / AppVeyor updates in place over the next few days. Contact has been made with the owners of the other modules to do the same. I did identify some issues in core Puppet around module loading on Windows, thanks to Ruby changing the behavior of Dir.glob when given 8.3 style paths - that ticket is at https://tickets.puppetlabs.com/browse/PUP-6557 / PR is at https://github.com/puppetlabs/puppet/pull/5156 and should be merged shortly. Thanks! Ethan J. Brown Tech Lead, Windows Engineering -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/056d604d-6311-4948-8e14-ef305086a03a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
