Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2917

Switch ci.jenkins.io to JCasC: agents

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      In order to improve our ability to operate ci.jenkins.io and efficiently update its configuration with trust and confidence, we should use JCasc.

      JCasC will not cover ALL the configuration items (thinking about the per-folder credentials), but would allow better improvement and reproducibility.

      • Install the JCasc Plugin
      • Create an initial configuration in the Puppet templates
      • Define the configuration items to migrate
      • Define the credentials from the Puppet encryption into the JCasC env. variables for credentials

      (As a reference and archive: A first try was done to migrate ci.j in Kubernetes with JCasc by Tim Jacomb here: https://github.com/jenkins-infra/charts/pull/174 )

        Attachments

          Activity

          dduportal Damien Duportal created issue -
          dduportal Damien Duportal made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          dduportal Damien Duportal made changes -
          Description In order to improve our ability to operate ci.jenkins.io and efficiently update its configuration with trust and confidence, we should use JCasc.

          JCasC will not cover ALL the configuration items (thinking about the per-folder credentials), but would allow better improvement and reproducibility.

          * (/) Install the JCasc Plugin
          * (x) Create an initial configuration in the Puppet templates
          * (x) Define the configuration items to migrate
          * (x) Define the credentials from the Puppet encryption into the JCasC env. variables for credentials

          (As a reference and archive: A first try was done to migrate ci.j in Kubernetes with JCasc by [~timjacomb] here: https://github.com/jenkins-infra/charts/pull/174 )
          In order to improve our ability to operate ci.jenkins.io and efficiently update its configuration with trust and confidence, we should use JCasc.

          JCasC will not cover ALL the configuration items (thinking about the per-folder credentials), but would allow better improvement and reproducibility.

          * (/) Install the JCasc Plugin
          * (/) Create an initial configuration in the Puppet templates
          * (/) Define the configuration items to migrate
          * (/) Define the credentials from the Puppet encryption into the JCasC env. variables for credentials

          (As a reference and archive: A first try was done to migrate ci.j in Kubernetes with JCasc by [~timjacomb] here: https://github.com/jenkins-infra/charts/pull/174 )
          dduportal Damien Duportal made changes -
          Summary Switch ci.jenkins.io to JCasC Switch ci.jenkins.io to JCasC: agents
          dduportal Damien Duportal made changes -
          Status In Progress [ 3 ] Open [ 1 ]
          dduportal Damien Duportal made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]

            People

            Assignee:
            dduportal Damien Duportal
            Reporter:
            dduportal Damien Duportal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: