Actions
Feature #18564
open[art] run jenkins release build steps with a set of parameters
Story points:
-
Release:
Release relationship:
Auto
Description
Maybe something like this:
1. Start a release with version number and git commits
2. Make it possible to run the appropriate jenkins jobs with those settings, individually
3. As part of 2, automatically update the redmine release ticket with the jenkins run IDs and version number / git commit
Related issues
Updated by Peter Amstutz almost 3 years ago
- Target version changed from 2022-01-05 sprint to 2022-01-19 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-01-19 sprint to 2022-02-16 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-02-16 sprint to 2022-03-02 sprint
Updated by Ward Vandewege over 2 years ago
- Related to Idea #18093: [art] Write script for Redmine that creates a new release process ticket added
Updated by Ward Vandewege over 2 years ago
Maybe something like this:
art release create -n 2.4.0 -p project_id -s sprint_id -g arvados=011742f3936e88338e7a2e3f2d92e74b89361958 -g arvados-workbench2=c0bbd8e4f7c38eacece83de646afe2b5689c6b86This would
- do `art redmine issues create-release-issue -n 2.4.0 -p project_id -s sprint_id -json` which will give us a redmine release ID (will it? check)
- add the git hashes to the release ticket
- create some local state? Or maybe we can just come up with a formatting convention that lets us use the release ticket to keep the git hash state
- kick off the appropriate jenkins jobs for the git hashes
and
art release update -r release_id -g arvados=011742f3936e88338e7a2e3f2d92e74b89361958 -g arvados-workbench2=c0bbd8e4f7c38eacece83de646afe2b5689c6b86which would
- update the git hashes for the release
- kick off the appropriate jenkins jobs for the git hashes
and
art release test -r release_idwhich would
- kick off the appropriate jenkins jobs for the git hashes
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-03-02 sprint to 2022-03-16 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-03-16 sprint to 2022-03-30 Sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-03-30 Sprint to 2022-04-13 Sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-04-13 Sprint to 2022-05-11 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-05-11 sprint to 2022-05-25 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-05-25 sprint to 2022-06-08 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-06-08 sprint to 2022-06-22 Sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-06-22 Sprint to 2022-07-20
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-07-20 to 2022-08-17 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-08-17 sprint to 2022-09-14 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-09-14 sprint to 2022-09-28 sprint
Updated by Peter Amstutz about 2 years ago
- Target version deleted (
2022-09-28 sprint)
Actions