Issue #3915 has been updated by Ken Barber.
No idea. I'd say its easier though to run tests in a chroot environment with CPAN modules - so I would imagine its not as much of a problem. Looks like now CPAN is largely tested by bots anyway: http://wiki.cpantesters.org/wiki/SmokeTools Puppet stuff on the other hand often needs a full environment with root access as well to prove things work as intended. I think generally the problem of testing puppet is a big factor here :-). I would say for now volunteers would have to just be careful and read code before execution - and just never test on their own desktops our prod systems :-). Virt envs would be best so you can roll them back periodically. ---------------------------------------- Feature #3915: System should provide testing and validation workflow http://projects.puppetlabs.com/issues/3915 Author: Ken Barber Status: Accepted Priority: Normal Assigned to: Igal Koshevoy Category: module site Target version: Keywords: Branch: Affected URL: CPAN has a testing workflow - so upon package submission volunteer testers can provide feedback on test runs: http://search.cpan.org/~kbarber/DotLock-1.06/ http://www.cpantesters.org/distro/D/DotLock.html#DotLock-1.06 This is provided as an automatic service to module developers and users - so upon uploading a new revision testers find and run the tests when they have time. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
