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
-
-
-
- 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
-