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

Automating release of Jenkins

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: ci, spof
    • Labels:
      None
    • Epic Name:
      Automating release of Jenkins
    • Similar Issues:

      Description

      Todo:

      • War signing
      • Windows installer signing
      • Agents
        • Win
        • Mac
      • What requirements would there be for building and signing a release in Jenkins?

      Ideal release manager workflow:

      1. Navigate to trusted.ci.jenkins.io
      2. Enter Git SHA1 and release version number
      3. Jenkins builds all the artifacts for the release (wars, containers, packages, installers)
      4. Any smoke-testing possible
      5. Publish the built artifacts to their respective repositories
      6. Email notification(s) to release manager(s) regardless of success/failure

        Attachments

          Issue Links

          is blocked by

          Task - A task that needs to be done. INFRA-601 Add Mac agent donated by maccloud.me

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Task - A task that needs to be done. INFRA-606 should have a windows agent or three

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. INFRA-545 Kohsuke is the only one to perform Jenkins release

          • Major - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-49905 Jenkins core build should verify Remoting code signing during the release

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

            Hide
            Permalink
            slide_o_mix Alex Earl added a comment -

            As part of this, for Windows, we will want to deploy to Chocolatey after building and signing the MSI (since the Chocolatey package needs the SHA of the MSI file to create the Chocolatey package). This would require a Chocolatey API key in the path for publishing.

            Show
            slide_o_mix Alex Earl added a comment - As part of this, for Windows, we will want to deploy to Chocolatey after building and signing the MSI (since the Chocolatey package needs the SHA of the MSI file to create the Chocolatey package). This would require a Chocolatey API key in the path for publishing.

              People

              Assignee:
              olblak Olivier Vernin
              Reporter:
              rtyler R. Tyler Croy
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated: