Jira (PUP-4492) Investigate: plan for module testing with puppet-agent

[Justin Stoller (JIRA)]

Title: Message Title

Justin Stoller commented on PUP-4492   Re: Investigate: plan for module testing with puppet-agent For spec level testing currently module authors can continue to use Facter 2. And hopefully an SDK will provide that functionality later on. (Though there's been discussion about shipping compiled gems if the SDK isn't going to be until after Puppet 5, and I think that Eric Sorenson owns that convo) As far as acceptance testing goes there's a small amount of Beaker updates and a chain of module team work that culminates in testing the modules against AIO in PE: QENG-2371 (supported modules are only technically supported against PE releases). That chain AFAICT is roughly: Module team updates supported modules to include puppet 4 via gem in spec testing on travis (as a non-failing cell) Module team to triage failures, ticket issues Once the module team is ready to turn puppet 4 on in CI spec tests we'll do that (QENG-2374) (either when they've fixed the issues in an ad hoc way, or their ready for it to be their primary focus and have their board go red) Once specs are green we'll enable testing of the puppet-agent package in the FOSS.next stage of their pipelines (QENG-2372, requires BKR-195) The module team will fix any issues that arise with that Once FOSS.next is stable green, we'll migrate the puppet-agent to be the FOSS.stable step in their pipeline. We'll remove the FOSS.next step and replay it with a FOSS.legacy step that tests old puppet 3.x compat (QENG-2373 a CI maintenance task) After the FOSS issues have been ironed out and SG goes code complete we'll re-enable the PE.next step in the pipelines and make sure they point at SG (QENG-2371, BKR-252). Then the module team will fix any issues that shake out from SG integrations with puppet-agent. I've ticket the work that I think needs ticketing. I believe the module team is in the process of ticketing what work they can (though it may just be "triage failures" that this point). Either way I think FM-2657 is the place for the action. 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.