Launch .gitlab-ci.yml jobs locally
Project description
gitlabci-local
Launch .gitlab-ci.yml jobs locally, wrapped inside the specific images,
with inplace project volume mounts and adaptive user selections.
Purpose
The main purpose of this project is to unify and enhance reliability
of builds, tests or releases running on GitLab CI in a similar local context,
by providing the simplicity of an interactive and automated terminal tool
and avoiding code duplication (Makefile, Shell scripts, docker run, ...).
Rather than creating yet another standard, the .gitlab-ci.yml specification
is the common and unique interface between GitLab CI and gitlabci-local.
Preview
Usage
usage: gitlabci-local [-h] [-q] [-c CONFIGURATION] [-B] [-A] [-m] [-n NETWORK]
[-p] [-e ENV] [-R] [-t TAGS] [-v VOLUME] [-w WORKDIR]
[--all] [--defaults] [--bash | --debug]
[-d | -s | -l | --pull] [names [names ...]]
gitlabci-local: Launch .gitlab-ci.yml jobs locally (aliases: gcil)
positional arguments | |
---|---|
names | Names of specific jobs (or stages with --pipeline) Regex names is supported unless --no-regex is used |
optional arguments | |
---|---|
-h, --help | Show this help message |
-q, --quiet | Hide jobs execution context |
-c CONFIGURATION | Path to the .gitlab-ci.yml configuration |
-B, --no-before | Disable before_script executions |
-A, --no-after | Disable after_script executions |
-m, --manual | Allow manual jobs to be used |
-n NETWORK | Configure the network mode used Choices: bridge, host, none. Default: bridge |
-p, --pipeline | Run complete stages rather than jobs |
-e ENV | Define VARIABLE=value, pass VARIABLE or ENV file |
-R, --no-regex | Disable regex search of names |
-t TAGS | Handle listed tags as manual jobs Default list: ['deploy', 'local', 'publish'] |
-v VOLUME | Mount VOLUME or HOST:TARGET in Docker containers |
-w WORKDIR | Override the container's working path |
--all | Enable all jobs by default in selections |
--defaults | Use default variables for .local:configurations |
--bash | Prepare runners for manual bash purposes |
--debug | Keep runners active for debugging purposes |
-d, --dump | Dump parsed .gitlab-ci.yml configuration |
-s, --select | Force jobs selection from enumerated names |
-l, --list | Select one job to run (implies --manual) |
--pull | Pull Docker images from all jobs |
User configurations with ".local:configurations"
gitlabci-local implements support for specific user configurations
allowing simple and interactive local pipeline configurations.
Supported user configurations include boolean
, choice
, input
, yaml
and json
.
Examples for each of these can be found in the configurations
unit tests: tests/configurations
Additional features in ".local"
gitlabci-local implements further support of most parameters
inside the .local
to ease default parameters definitions.
Supported local values include after
, all
, bash
, before
, configurations
, debug
, defaults
,
env
, image
, manual
, names
, network
, pipeline
, quiet
, tags
, volumes
, workdir
.
Examples for each of these can be found in the local
unit tests: tests/local
Job execution in native context
gitlabci-local runs every jobs in the specified Docker image.
For specific local purposes where the native host context is wished,
where the host tools, folders or credentials are required,
image: local
can be used to run the scripts natively.
An example usage can be found in the local Changelog
job: .gitlab-ci.yml
Environment variables
gitlabci-local uses the variables defined in .gitlab-ci.yml,
parses the simple environment variables file named .env
and the configurations selected through .local:configurations
.
If specific environment variables are to be used in the job's container:
-e VARIABLE
: pass an environment variable-e VARIABLE=value
: set a variable to a specific value-e ENVIRONMENT_FILE
: parse a file as default variables
For example, -e TERM=ansi
may enable colored terminal outputs.
The variable CI_LOCAL
is automatically defined to true
by gitlabci-local
to allow specific conditions for local purposes in jobs' scripts.
Windows compatibility
In order to access the interactive terminal user interfaces,
Windows users may need to allocate an interactive PTY context
through the winpty
wrapper, for example winpty gitlabci-local
.
Supported .gitlab-ci.yml features
- image: IMAGE_NAME
- image:
- name: IMAGE_NAME
- entrypoint: ['COMMANDS']
- include:
- local: FILE_PATHS
- variables:
- VARIABLES: VALUES
- .TEMPLATES: &TEMPLATES
- stages:
- STAGE_NAMES
- before_script:
- COMMANDS
- after_script:
- COMMANDS
- JOB_NAME:
- stage: STAGE_NAME
- image: IMAGE_NAME
- image:
- name: IMAGE_NAME
- entrypoint: ['COMMANDS']
- <<: *TEMPLATES
- extends: TEMPLATE
- extends:
- TEMPLATES
- variables:
- VARIABLES: VALUES
- before_script:
- COMMANDS
- script:
- COMMANDS
- after_script:
- COMMANDS
- retry: RETRY_COUNT
- retry:
- max: RETRY_COUNT
- tags:
- MANUAL_TAGS
- when: on_success/manual/on_failure/always
- allow_failure: true/false
Dependencies
- colored: Terminal colors and styles
- docker: Docker Engine API
- oyaml: Ordered YAML dictionnaries
- PyInquirer: Interactive terminal user interfaces
- python-dotenv: Support for .env files parsing
References
- .gitlab-ci.yml: GitLab CI/CD Pipeline Configuration Reference
- git-chglog: CHANGELOG generator
- peek: Simple GIF screen recorder
- pexpect: Interactive console applications controller
- PyPI: The Python Package Index
- winpty: Windows PTY interface wrapper
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
Hashes for gitlabci_local-1.3.1-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 1e744704dfaf5d8646f7dc4d3e53a8fd8240c718a71b249039f2d4fdd12de0bb |
|
MD5 | 31df1652e034ea833ae0cceaa12c44fc |
|
BLAKE2b-256 | 2a6cccc7f31f370e1a5202a3d0362d51109c6f2996eec5bf48cda43d1e812bd1 |