[Puppet-dev] Feature proposal: external environment locator (EEL)
Hi all, I would like to propose a new feature for puppet master: External Environment Locator (EEL) The main objective would be to make locating puppet environment locations more flexible compared to directory environments. Basic functionality would facilitate usage of external program to convert environment name to corresponding path (directory or environment configuration file). To be able to achieve this, two new settings would need to be introduced: 1. env_terminus - possibla values: 'directory' and 'exec', 'directory' being the default one (retains current directory environments functionality) 2. external_env - path to executable, if 'exec' is used in the setting above Sample configuration: - [master] env_terminus = exec external_env = /path/to/external/environment/locator.sh -- EEL (locator.sh) requirements would be defined with the following specification: It takes one argument: - requested environment name (once node and ENC agree on node environment) It returns one path, to directory or to file: - if returned path is a directory, that is used as environment path, seeking environment.conf inside it, or using defaults (based on returned path) if not found; - if returned path is a file, then that is treated as path to environment.conf. which should be opened and parsed for additional environment configuration. If file does not exist, or some settings are not set, then dirname() is used to determine path to environment and defaults are based on that value (moduledir and manifest) After that, all the normal rules apply. I would like to hear your opinion about this, and whether this would be useful for you. Best regards, b. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/13559aa4-2760-43dc-a619-26e27630a8b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] rspec-puppet is not being maintained
Hello all, Wanted to share a pointer to Issue #260 on rspec-puppet https://github.com/rodjek/rspec-puppet/issues/260, which is a proposal for getting rspec-puppet the maintenance attention it needs by transferring it to the Puppet Community org. I've been trying to resolve the lack-of-maintenance issue for almost two months with little progress. There's support in the community, but still no PRs merged and no ACKs from rodjek. Are there any Puppet community managers/leaders who would be willing to help drive this? I think addressing it ASAP is pretty critical for Puppet's health. Thanks, Daniel Farrell Software Engineer, Red Hat SDN Team https://twitter.com/dfarrell07 -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/70616ed5-5528-489c-9edc-c5454467ed64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: Rspec tests on puppet master branch failing
On 2015-12-03 16:40, Trevor Vaughan wrote: Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Does it work if you run the failing tests in isolation? (If so it could be an ordering problem). I just ran this on master: * bundle update * bundle exec rake parallel:spec[4] = 18768 examples, 0 failures, 44 pending - henrik Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a626981__36338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindberg@cloudsmith.__com mailto:henrik.lindb...@cloudsmith.com mailto:henrik.lindberg@__cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tel:%28410%29%20541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com__ -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com mailto:puppet-dev+__unsubscr...@googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/CANs%__2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/__msgid/puppet-dev/CANs%__2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com?utm_medium=email__utm_source=footer https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.__blogspot.se/ http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/mdsab4%24uit%__241%40ger.gmane.org https://groups.google.com/d/msgid/puppet-dev/mdsab4%24uit%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com mailto:puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoVKj5nYqz2Ogbn-LZi%3DMbpTOPftKr%2Bz6gCpmD9Ss-rkLA%40mail.gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoVKj5nYqz2Ogbn-LZi%3DMbpTOPftKr%2Bz6gCpmD9Ss-rkLA%40mail.gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe
Re: [Puppet-dev] Re: Rspec tests on puppet master branch failing
Just for additional info. When I run 'bundle update' I get the following output from the latest HEAD in master: Installing rake 10.1.1 Installing CFPropertyList 2.2.8 Installing ast 2.0.0 Installing parser 2.2.0.3 Installing astrolabe 1.3.0 Installing builder 3.2.2 Installing coderay 1.1.0 Installing diff-lcs 1.2.5 Installing facter 2.4.1 Installing json_pure 1.8.2 Installing hiera 1.3.4 Installing json 1.8.2 Installing json-schema 2.1.1 Installing metaclass 0.0.4 Installing method_source 0.8.2 Installing mocha 0.10.5 Installing msgpack 0.5.11 Installing multi_json 1.7.7 Installing net-ssh 2.9.2 Installing powerpack 0.0.9 Installing slop 3.6.0 Installing pry 0.10.1 Using puppet 4.0.0 (was 3.7.3) from source at /home/user/puppet Installing puppet-lint 1.1.0 Installing puppet-syntax 2.0.0 Installing rspec-support 3.2.2 Installing rspec-core 3.2.2 Installing rspec-expectations 3.2.0 Installing rspec-mocks 3.2.1 Installing rspec 3.2.0 Installing rspec-puppet 1.0.1 Installing puppetlabs_spec_helper 0.9.1 Installing racc 1.4.9 Installing rack 1.6.0 Installing rainbow 2.0.0 Installing rdoc 4.2.0 Installing redcarpet 2.3.0 Installing rspec-collection_matchers 1.1.2 Installing rspec-its 1.2.0 Installing rspec-legacy_formatters 1.0.0 Installing ruby-progressbar 1.7.1 Installing rubocop 0.26.1 Installing ruby-prof 0.15.6 Installing thread_safe 0.3.5 Installing tzinfo 1.2.2 Installing yard 0.8.7.6 Installing yarjuf 2.0.0 Using bundler 1.6.2 Your bundle is updated! On Thu, Mar 12, 2015 at 12:01 PM, Trevor Vaughan tvaug...@onyxpoint.com wrote: No, if I run parallel::spec, I actually get different errors, so I stopped trying to use it. I just ran with a clean ruby 2.0.0-p353 with the same results. Not quite sure what's going on. I'll poke around some more later since you can't seem to reproduce. Trevor On Thu, Mar 12, 2015 at 11:57 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 16:40, Trevor Vaughan wrote: Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Does it work if you run the failing tests in isolation? (If so it could be an ordering problem). I just ran this on master: * bundle update * bundle exec rake parallel:spec[4] = 18768 examples, 0 failures, 44 pending - henrik Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a626981__36338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindberg@cloudsmith.__com mailto:henrik.lindb...@cloudsmith.com mailto:henrik.lindberg@__cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tel:%28410%29%20541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com __ -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com mailto:puppet-dev+__unsubscr...@googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail. __gmail.com?utm_medium=email__utm_source=footer https://groups.google.com/d/msgid/puppet-dev/CANs%
Re: [Puppet-dev] Re: Rspec tests on puppet master branch failing
Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a62698136338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com mailto:puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail. gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-dev/mdsab4%24uit%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoVKj5nYqz2Ogbn-LZi%3DMbpTOPftKr%2Bz6gCpmD9Ss-rkLA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: Rspec tests on puppet master branch failing
No, if I run parallel::spec, I actually get different errors, so I stopped trying to use it. I just ran with a clean ruby 2.0.0-p353 with the same results. Not quite sure what's going on. I'll poke around some more later since you can't seem to reproduce. Trevor On Thu, Mar 12, 2015 at 11:57 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 16:40, Trevor Vaughan wrote: Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Does it work if you run the failing tests in isolation? (If so it could be an ordering problem). I just ran this on master: * bundle update * bundle exec rake parallel:spec[4] = 18768 examples, 0 failures, 44 pending - henrik Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a626981__36338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindberg@cloudsmith.__com mailto:henrik.lindb...@cloudsmith.com mailto:henrik.lindberg@__cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tel:%28410%29%20541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com__ -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com mailto:puppet-dev+__unsubscr...@googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail. __gmail.com?utm_medium=email__utm_source=footer https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail. gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.__blogspot.se/ http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/mdsab4%24uit% __241%40ger.gmane.org https://groups.google.com/d/msgid/puppet-dev/mdsab4%24uit% 241%40ger.gmane.org. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com mailto:puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoVKj5nYqz2Ogbn-LZi%
[Puppet-dev] [announce] new home for beaker bugs
Beaker bugs now have their own, public Jira project: https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20BKR I have shut down our beaker github issue tracker and transitioned all open/unresolved issues to this new project. Please feel free to create/edit bugs! Thanks, Your friendly beaker team. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/0964b78b-e7ae-4392-855a-d25ca4d5d145%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: Rspec tests on puppet master branch failing
On Thu, Mar 12, 2015 at 9:01 AM, Trevor Vaughan tvaug...@onyxpoint.com wrote: No, if I run parallel::spec, I actually get different errors, so I stopped trying to use it. I just ran with a clean ruby 2.0.0-p353 with the same results. As Henrik mentioned, it could be a spec order problem. If you run: bundle exec rake ci:spec then you should get a shiny spec_order.txt. Then you can run: util/binary_search_specs.rb full path to failing spec And it will (usually) tell you the test that makes the failing spec fail. (The 'usually' caveat is because there can be spec failures that require specific ordering between 2 spec files, and this tool only handles the case for 2 spec files. The 2 case is super duper fun.) Clearly, this needs to be in our docs, PR coming. Kylo Not quite sure what's going on. I'll poke around some more later since you can't seem to reproduce. Trevor On Thu, Mar 12, 2015 at 11:57 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 16:40, Trevor Vaughan wrote: Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Does it work if you run the failing tests in isolation? (If so it could be an ordering problem). I just ran this on master: * bundle update * bundle exec rake parallel:spec[4] = 18768 examples, 0 failures, 44 pending - henrik Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a626981__36338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindberg@cloudsmith.__com mailto:henrik.lindb...@cloudsmith.com mailto:henrik.lindberg@__cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tel:%28410%29%20541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com __ -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com mailto:puppet-dev+__unsubscr...@googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail. __gmail.com?utm_medium=email__utm_source=footer https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail. gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.__blogspot.se/ http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/mdsab4%24uit% __241%40ger.gmane.org https://groups.google.com/d/msgid/puppet-dev/mdsab4%24uit% 241%40ger.gmane.org. For more options, visit https://groups.google.com/d/__optout
[Puppet-dev] Re: Feature proposal: external environment locator (EEL)
On Wednesday, March 11, 2015 at 11:56:44 AM UTC-5, Bostjan Skufca wrote: Hi all, I would like to propose a new feature for puppet master: External Environment Locator (EEL) The main objective would be to make locating puppet environment locations more flexible compared to directory environments. Basic functionality would facilitate usage of external program to convert environment name to corresponding path (directory or environment configuration file). Greater flexibility is not a justification in itself. Just because I wouldn't use such a feature doesn't mean it's not worthy, but I would like to hear a bit about how you imagine using it, and in what other situations you imagine it being useful. John -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/2e6fee93-b5af-4dab-8693-4fa56f691f75%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Feature proposal: external environment locator (EEL)
On 03/11/2015 05:56 PM, Bostjan Skufca wrote: I would like to hear your opinion about this, and whether this would be useful for you. Hi, I don't believe that such a feature would be useful to a majority of users, myself included. I do see two disadvantages to adding this: 1. It adds complexity, of which there is no shortage as far as environments are concerned, at least that's my gut feeling. 2. It adds configuration options, so there is additional complexity for the end user as well. I'm not saying we should remove as many configuration settings and options as possible, but we shouldn't go overboard with new ways for users to shoot themselves in the foot. Cheers, Felix -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/550213D9.1090305%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: Feature proposal: external environment locator (EEL)
Neat idea. I would consider using this for automatic git-checkout of project branches, rather than preemptively checking out all branches by cron or git-hook. On Thu, Mar 12, 2015 at 3:33 PM, Bostjan Skufca bostjan.skufca.w...@gmail.com wrote: On Thursday, 12 March 2015 20:30:23 UTC+1, John Bollinger wrote: On Wednesday, March 11, 2015 at 11:56:44 AM UTC-5, Bostjan Skufca wrote: Hi all, I would like to propose a new feature for puppet master: External Environment Locator (EEL) The main objective would be to make locating puppet environment locations more flexible compared to directory environments. Basic functionality would facilitate usage of external program to convert environment name to corresponding path (directory or environment configuration file). Greater flexibility is not a justification in itself. Just because I wouldn't use such a feature doesn't mean it's not worthy, but I would like to hear a bit about how you imagine using it, and in what other situations you imagine it being useful. John, please see here (in 9th message on this other thread I explained my use case), this is a direct link to that message: https://groups.google.com/d/msg/puppet-dev/Akk8vZBPuRs/sB71tK5ow1UJ b. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/56c3e851-b315-48e9-a2f9-ed3e0b2e4c16%40googlegroups.com https://groups.google.com/d/msgid/puppet-dev/56c3e851-b315-48e9-a2f9-ed3e0b2e4c16%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAEdAYKU88eGXJ3O5_v4AJ0Hd9jUakP0-LKLiyoeRBR9PnVWkKQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: Feature proposal: external environment locator (EEL)
On Thursday, 12 March 2015 20:30:23 UTC+1, John Bollinger wrote: On Wednesday, March 11, 2015 at 11:56:44 AM UTC-5, Bostjan Skufca wrote: Hi all, I would like to propose a new feature for puppet master: External Environment Locator (EEL) The main objective would be to make locating puppet environment locations more flexible compared to directory environments. Basic functionality would facilitate usage of external program to convert environment name to corresponding path (directory or environment configuration file). Greater flexibility is not a justification in itself. Just because I wouldn't use such a feature doesn't mean it's not worthy, but I would like to hear a bit about how you imagine using it, and in what other situations you imagine it being useful. John, please see here (in 9th message on this other thread I explained my use case), this is a direct link to that message: https://groups.google.com/d/msg/puppet-dev/Akk8vZBPuRs/sB71tK5ow1UJ b. -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/56c3e851-b315-48e9-a2f9-ed3e0b2e4c16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet-dev] Re: Puppet PR Triage for 2015-03-11 starting soon
Hi Melissa, Thank you very much for posting the triage videos and notes I find them very useful to hear first hand thoughts on various PR's. If it hasn't already been suggested and rejected before I think a useful addition might be to keep a stop watch running during the recording and include a rough (+x minutes) against the notes for each PR's. It would make it easier to skim through to areas of interest and also it would be useful if people ever want to go back and see what was discussed regarding a particular issue they don''t need to watch the whole thing. Thanks, Peter On Thursday, 12 March 2015 09:12:10 UTC+11, Melissa Stone wrote: Triage notes are available at https://github.com/puppet-community/community-triage/blob/master/core/notes/2015-03-11.md On Wed, Mar 11, 2015 at 9:57 AM, Melissa Stone mel...@puppetlabs.com javascript: wrote: Starting the PR triage for puppet/facter/hiera/puppet-server soon at http://links.puppetlabs.com/pr-triage -- Melissa Stone Release Engineer, Puppet Labs -- *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- Melissa Stone Release Engineer, Puppet Labs -- *PuppetConf 2015 http://2015.puppetconf.com/ is coming to Portland, Oregon! Join us October 5-9.* *Register now to take advantage of the Early Adopter discount https://www.eventbrite.com/e/puppetconf-2015-october-5-9-tickets-13115894995?discount=EarlyAdopter * *—**save $349!* -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/d5476a93-ad5a-49cf-bb8c-c04276cbfaca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet-dev] Re: Rspec tests on puppet master branch failing
This file appears to be the issue according to the binary search (neat tool BTW) The culprit is /home/thanos/Work/puppet/spec/integration/agent/logging_spec.rb. However, when I run that file by hand, it works just fine. The issues do specifically seem to be related to the Package tests from what I can tell. For completeness: Fedora 20 Ruby 2.0.0-p353 Thanks, Trevor On Thu, Mar 12, 2015 at 3:14 PM, Kylo Ginsberg k...@puppetlabs.com wrote: On Thu, Mar 12, 2015 at 9:01 AM, Trevor Vaughan tvaug...@onyxpoint.com wrote: No, if I run parallel::spec, I actually get different errors, so I stopped trying to use it. I just ran with a clean ruby 2.0.0-p353 with the same results. As Henrik mentioned, it could be a spec order problem. If you run: bundle exec rake ci:spec then you should get a shiny spec_order.txt. Then you can run: util/binary_search_specs.rb full path to failing spec And it will (usually) tell you the test that makes the failing spec fail. (The 'usually' caveat is because there can be spec failures that require specific ordering between 2 spec files, and this tool only handles the case for 2 spec files. The 2 case is super duper fun.) Clearly, this needs to be in our docs, PR coming. Kylo Not quite sure what's going on. I'll poke around some more later since you can't seem to reproduce. Trevor On Thu, Mar 12, 2015 at 11:57 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 16:40, Trevor Vaughan wrote: Hi Henrik, I purged all of my gems removed my Gemfile.lock file and then ran bundle install followed by bundle update with the same result. Does it work if you run the failing tests in isolation? (If so it could be an ordering problem). I just ran this on master: * bundle update * bundle exec rake parallel:spec[4] = 18768 examples, 0 failures, 44 pending - henrik Thanks, Trevor On Thu, Mar 12, 2015 at 11:11 AM, Henrik Lindberg henrik.lindb...@cloudsmith.com mailto:henrik.lindb...@cloudsmith.com wrote: On 2015-12-03 14:10, Trevor Vaughan wrote: Hi all, Some of the package spec tests are failing for me under Ruby 1.9.3. The offending commit appears to be: commit 8eb9557420bd10cfb268c55a626981__36338c9b79 Merge: 0abb9a9 11bba86 Author: Henrik Lindberg henrik.lindberg@cloudsmith.__com mailto:henrik.lindb...@cloudsmith.com mailto:henrik.lindberg@__cloudsmith.com mailto:henrik.lindb...@cloudsmith.com Date: Thu Mar 5 22:50:14 2015 +0100 Merge branch 'stable' Conflicts: lib/puppet/parser/scope.rb lib/puppet/type/package.rb spec/unit/type/package_spec.rb Changed be_true matcher to be_truthy because of rspec version change Ruby Version: ruby-1.9.3-p551 Gemfile: Stock in Puppet core Branch: master (stable is fine) You probably do not have rspec 3 which is now required on master. Try a 'bundle update' - henrik Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tel:%28410%29%20541-6699 tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com mailto:tvaug...@onyxpoint.com __ -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscribe@__googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com mailto:puppet-dev+__unsubscr...@googlegroups.com mailto:puppet-dev%2bunsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail.__gmail.com https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail.gmail.com https://groups.google.com/d/__msgid/puppet-dev/CANs%__ 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT___mLucay%3D9oXe-kQU9PQ%40mail. __gmail.com?utm_medium=email__utm_source=footer https://groups.google.com/d/msgid/puppet-dev/CANs% 2BFoXR9dtAJ5x4qk4vwrK14CRGxyT_mLucay%3D9oXe-kQU9PQ%40mail. gmail.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/__optout https://groups.google.com/d/optout. -- Visit my Blog Puppet on the Edge http://puppet-on-the-edge.__blogspot.se/ http://puppet-on-the-edge.blogspot.se/ -- You received this message because you are subscribed to the Google Groups Puppet Developers group. To
