Identical Job ID Resolution Strategy for Retry/ Trace
Problem to solve
A different resolution strategy is currently used to determine the jobId for glab ci retry
and glab ci trace
.
-
retry
- resolve with
glab ci retry <job-id>
args
- resolve with
-
trace
- resolve with
glab ci trace <job-id>
args - allow interactive resolve of job-id using pipeline ask-prompt (
glab ci trace
)
- resolve with
However, the job id is neither displayed to the user in gitlab ci get
nor in gitlab ci view
. Which is why a user actually want to use the name of the job and additionally use pipeline-id
(default: last pipeline) and branch (default: current branch), e.g. glab ci trace lint
Proposal
Allow using a jobId, jobName or interactive Job Resolution in all commands for ci (retry, trace, trigger, cancel?, ...)
$ glab ci trace
#=> interactively select a job to trace
$ glab ci trace 224356863
#=> trace job with id 224356863
$ glab ci trace lint
#=> trace job with name lint
Further details
This feature is mentioned in #682 (comment 1140044098) with new command trigger
but seems valid for all commands using only job-id