Pipelines help you automate steps in your software delivery process, such as initiating code builds, running automated tests, and deploying to a staging or production environment.
Conditions limit pipeline step execution at runtime. Gitness sets variables that can be used in conditions.
Expressions provide dynamic values to your pipeline at runtime.
A matrix strategy can be used to test multiple versions of tools in a single pipeline step definition.
Pipeline steps are executed sequentially by default. You can optionally run steps in parallel.
Secrets are used to store and manage sensitive information, such as passwords, tokens, and ssh keys. Storing this information in a secret is considered safer than storing it in your configuration file in plain text.
A stage contains one or more steps.
When code is pushed to a repository, a pull request is opened, or a tag is created, Gitness can automatically trigger pipeline execution.
Variables can be set at pipeline, stage and step levels.