Details
-
Type:
Epic
-
Status: Open (View Workflow)
-
Priority:
Critical
-
Resolution: Unresolved
-
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:
- Navigate to trusted.ci.jenkins.io
- Enter Git SHA1 and release version number
- Jenkins builds all the artifacts for the release (wars, containers, packages, installers)
- Any smoke-testing possible
- Publish the built artifacts to their respective repositories
- Email notification(s) to release manager(s) regardless of success/failure
Attachments
Issue Links
- is blocked by
-
INFRA-601 Add Mac agent donated by maccloud.me
-
- Closed
-
-
INFRA-606 should have a windows agent or three
-
- Closed
-
- is duplicated by
-
INFRA-545 Kohsuke is the only one to perform Jenkins release
-
- Closed
-
- is related to
-
JENKINS-49905 Jenkins core build should verify Remoting code signing during the release
-
- Closed
-
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.