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

Remove cisco-wrlinux-5-x86_64, cisco-wrlinux-7-x86_64, cumulus-2.2-amd64, fedora-26-x86_64, eos-4-i386, el-6-s390x, el-7-s390x, sles-11-s390x, sles-12-s390x platform definition from puppet-agent repository

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: puppet-agent 6.0.0
    • Component/s: None
    • Labels:
      None
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      Needs Assessment

      Description

      Platform 6 OS platform removals (supersedes any OS platform lists in the body of this ticket)

      • cisco-wrlinux-5-x86_64
      • cisco-wrlinux-7-x86_64
      • cumulus-2.2-amd64
      • eos-4-i386
      • el-6-s390x
      • el-7-s390x
      • sles-11-s390x
      • sles-12-s390x
      • fedora-26-x86_64

      Process

      The work here consists of two steps that should be done in separate commits. The first step is to remove the platform from ext/build_defaults.yaml.

      The second step is to remove the platform.rb file in configs/platforms, and any special casing required for that specific platform. The latter may include, but is not limited to, any platform-specific files in the resources directory (e.g., patches, scripts), specific casing in the .rb files found in the configs/components and configs/projects directories, and special casing in the acceptance tests found in the acceptance directory.

      The agent repo has multiple maintenance branches as well as a master branch. If you are unsure about what branch to target your PR at, feel free to ping the Platform OS team. Note that you only need to make a PR to the lowest agent maintenance branch, since there is some merge-up automation already in place for the agent repo that will ensure your work gets merged-up to the later branches. Also make sure that the Platform OS team members review your PR.

      Context

      Removing the platform from ext/build_defaults.yaml in the first step ensures that we do not ship the built agent to our nightly repositories. The second step completely removes the platform and all mentions of it from the agent repository so that we cannot even build the agent; this is a more radical change. The main reason we create two commits here instead of one is due to an (unlikely) scenario where we want to stop shipping the platform but still test it out in CI (i.e., do only the first step).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              geoff.nichols Geoff Nichols
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support