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

Separate master and 6.0.x suite targets in ci-job-configs for puppet-runtime and puppet-agent

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      It's possible to add new platforms to puppet-agent CI for the 6.0.x branch but not the master branch. 
      It's possible to add new platforms to puppet-runtime CI only (and not puppet-agent) for all branches of puppet-agent.

      Show
      It's possible to add new platforms to puppet-agent CI for the 6.0.x branch but not the master branch.  It's possible to add new platforms to puppet-runtime CI only (and not puppet-agent) for all branches of puppet-agent.
    • Team:
      Night's Watch
    • Story Points:
      2
    • Sprint:
      PR - 2019-04-03, PR - 2019-04-17, PR - 2019-05-02
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment

      Description

      1. Right now, it is not possible to add a new platform to the puppet-agent pipelines for only the 6.0.x branch of puppet-agent and not master, because they share the same platforms. This hasn't caused any huge problems yet because 6.0.x and master haven't diverged very much, but it makes adding new platform support more dangerous, because new platforms that fail can break both the 6.0.x and master pipelines at once (as opposed to just 6.0.x). 
      2. Right now, it is not possible to add a new platform to the puppet-runtime pipelines for puppet-agent 6.0.x and master without also adding that platform to the puppet-agent pipelines. This is not ideal because it prevents developers who are adding a new platform from building and shipping 6.0.x & master runtimes until the puppet-agent built with the new platform have fully passed 5.5.x CI (this situation makes it tempting to add the platform to all puppet-agent branches at once, since that allows all the runtimes to be built.)

      Ideally we would solve this by using the metadata service (RE-9967) but neither RE nor Platform OS has the resources to do that right now. Instead, we'll need to duplicate the platform lists again in ci-job-configs, so that we have separate targets for 5.5.x, 6.0.x, and master.

      To address problem 1, this means duplicating the master_suite_targets as 60x_suite_targets here and using those new 6.0.x targets in the 6.0.x pipeline:

      https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml#L11

      For problem 2, this means duplicating the existing master and 6.0.x targets for puppet-runtime, the way that 5.5.x and 1.10.x have done here, and using those targets in the puppet-runtime pipelines for puppet-agent:

      https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml#L231

       

        Attachments

          Activity

            People

            • Assignee:
              sebastian.miclea Sebastian Miclea
              Reporter:
              casey.williams Casey Williams
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support