NAME¶

gcli pipelines — Inspect and manage GitLab Pipelines

SYNOPSIS¶

DESCRIPTION¶

gcli pipelines is used to display data about the Continuous Integration (CI) service of Gitlab. You can list pipelines of a given repository, list jobs in a given pipeline or perform actions such as restarting jobs or fetching their logs.

OPTIONS¶

-o, --owner owner

Operate on the repository of the given owner. This option can only be used in combination with -r.

-r, --repo repo

Operate on the given repository. This option can only be used in combination with -o.

-n, --count n

Fetch at least n items. Setting n to -1 will fetch all items. Default: 30. Note that on large repositories fetching all items can take a considerable amount of time and may result in rate limiting by the GitLab API.

-p, --pipeline pipeline-id

List jobs in the given pipeline.

-j, --jobs job

execute the given actions for the specified job.

ACTIONS¶

actions... may be one or more of the following:

log

Dump the log of the job.

status

Print a short summary of the job.

cancel

Cancel the job.

retry

Retry the job.

artifacts [-o outfile]

Download the artifacts archive as a zip to disk. The default output file is artifacts.zip but it can be overridden by using the -o flag.

EXAMPLES¶

Print a list of the last 30 pipelines in the current project:

$ gcli pipelines

List all jobs of pipeline #3316:

$ gcli pipelines -p3316

Dump the log of Job #423141 in herrhotzenplotz/gcli:

$ gcli pipelines -o herrhotzenplotz -r gcli -j 423141 log

SEE ALSO¶

git(1), gcli(1)

AUTHORS¶

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors.

BUGS¶

We are missing a -a flag. This is the current implied behaviour.

Please report bugs via E-Mail to ~herrhotzenplotz/gcli-discuss@lists.sr.ht.

Alternatively you can report them on any of the forges linked at https://herrhotzenplotz.de/gcli. However, the preferred and quickest method is to use the mailing list.