Uploaded image for project: 'Puppet Agent'
  1. Puppet Agent
  2. PA-562

Add a module smoke test to the Puppet Agent pipeline



    • Task
    • Status: Resolved
    • Major
    • Resolution: Done
    • None
    • None
    • None
    • None
      • One new stage in a puppet-agent CI pipeline, providing useful CI signal from 'puppet apply' style testing of at least one module.
      • Measure duration and success rate impact to pipeline.
    • Agent
    • 3
    • AP 2016-12-14, AP 2017-01-11, Agent 2017-03-22
    • No Action
    • N/A [mass update]: Various build, documentation, infra, or test-related issues


      This ticket is to add a test or set of tests of a Module to the Puppet Agent CI pipeline. Our modules tend to exercise the puppet code base in ways that our acceptance tests don't (yet) or at least they tend to surface regressions.

      In Scope

      • Add a test / stage to the puppet agent CI pipeline

      Open Questions

      • Which PA branch - stable? master? both?
      • How many / which tests to run?
      • Which module to use? (test against released modules)

      Similar to the work done in PA-477 the following identified modules need to be added.

      Recommended modules to add from FM-5640
      concat: cross-platform module rummaging in puppet's guts
      ntp: simple linux-only go-to module for all testing purposes
      apache: complex linux-only go-to module for all testing purposes
      stdlib: cross-platform high-use module
      acl: frequently used and fairly comprehensive Windows module

      Work To Do:


        Issue Links



              maggie Maggie Dreyer
              moses Moses Mendoza
              0 Vote for this issue
              5 Start watching this issue



                Zendesk Support