Project

General

Profile

Actions

Feature #18564

open

[art] run jenkins release build steps with a set of parameters

Added by Ward Vandewege 7 months ago. Updated 21 days ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
-

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


Subtasks 1 (1 open0 closed)

Task #18613: ReviewNewPeter Amstutz

Actions

Related issues

Related to Arvados - Story #18093: [art] Write script for Redmine that creates a new release process ticketResolvedWard Vandewege11/18/2021

Actions
Actions #1

Updated by Ward Vandewege 7 months ago

  • Description updated (diff)
Actions #2

Updated by Peter Amstutz 7 months ago

  • Target version changed from 2022-01-05 sprint to 2022-01-19 sprint
Actions #3

Updated by Peter Amstutz 6 months ago

  • Assigned To set to Ward Vandewege
Actions #4

Updated by Peter Amstutz 5 months ago

  • Target version changed from 2022-01-19 sprint to 2022-02-16 sprint
Actions #5

Updated by Peter Amstutz 4 months ago

  • Target version changed from 2022-02-16 sprint to 2022-03-02 sprint
Actions #6

Updated by Ward Vandewege 4 months ago

  • Related to Story #18093: [art] Write script for Redmine that creates a new release process ticket added
Actions #7

Updated by Ward Vandewege 4 months ago

Maybe something like this:

art release create -n 2.4.0 -p project_id -s sprint_id -g arvados=011742f3936e88338e7a2e3f2d92e74b89361958 -g arvados-workbench2=c0bbd8e4f7c38eacece83de646afe2b5689c6b86
This 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=c0bbd8e4f7c38eacece83de646afe2b5689c6b86
which would
  • update the git hashes for the release
  • kick off the appropriate jenkins jobs for the git hashes

and

art release test -r release_id
which would
  • kick off the appropriate jenkins jobs for the git hashes
Actions #8

Updated by Peter Amstutz 4 months ago

  • Target version changed from 2022-03-02 sprint to 2022-03-16 sprint
Actions #9

Updated by Peter Amstutz 4 months ago

  • Target version changed from 2022-03-16 sprint to 2022-03-30 Sprint
Actions #10

Updated by Peter Amstutz 3 months ago

  • Target version changed from 2022-03-30 Sprint to 2022-04-13 Sprint
Actions #11

Updated by Peter Amstutz 3 months ago

  • Target version changed from 2022-04-13 Sprint to 2022-05-11 sprint
Actions #12

Updated by Peter Amstutz 2 months ago

  • Target version changed from 2022-05-11 sprint to 2022-05-25 sprint
Actions #13

Updated by Peter Amstutz about 2 months ago

  • Target version changed from 2022-05-25 sprint to 2022-06-08 sprint
Actions #14

Updated by Peter Amstutz 22 days ago

  • Target version changed from 2022-06-08 sprint to 2022-06-22 Sprint
Actions #15

Updated by Peter Amstutz 21 days ago

  • Assigned To deleted (Ward Vandewege)
Actions #16

Updated by Peter Amstutz 21 days ago

  • Target version changed from 2022-06-22 Sprint to 2022-07-20
Actions

Also available in: Atom PDF