-
semantic-release-bot authored
# [2.1.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.0.0...2.1.0) (2022-10-05) ### Features * trigger gitleaks jobs without any needs leveraging Gitlab CI DAG ([bbf166f4](https://gitlab.com/to-be-continuous/gitleaks/commit/bbf166f47785df0bacb115f47e2cbf56330c8bce))
semantic-release-bot authored# [2.1.0](https://gitlab.com/to-be-continuous/gitleaks/compare/2.0.0...2.1.0) (2022-10-05) ### Features * trigger gitleaks jobs without any needs leveraging Gitlab CI DAG ([bbf166f4](https://gitlab.com/to-be-continuous/gitleaks/commit/bbf166f47785df0bacb115f47e2cbf56330c8bce))
README.md 1.77 KiB
GitLab CI template for Gitleaks
This project implements a generic GitLab CI template for Gitleaks.
When run on the master branch, Gitleaks will audit all commits from all branches.
When run on other branches, Gitleaks will run a quick analysis on the current branch.
Usage
In order to include this template in your project, add the following to your gitlab-ci.yml:
include:
- project: 'to-be-continuous/gitleaks'
ref: '2.1.0'
file: '/templates/gitlab-ci-gitleaks.yml'
gitleaks jobs configuration
Those jobs trigger a Gitleaks analysis (either on the complete repository, either on the current branch). They use the following configuration.
| Name | description | default value |
|---|---|---|
GITLEAKS_IMAGE |
The Docker image used to run Gitleaks | zricethezav/gitleaks:latest |
GITLEAKS_RULES |
Gitleaks configuration rules to use (you may also provide your own .gitleaks.toml configuration file in your project). |
none (uses default rules) |
GITLEAKS_ARGS |
Options for a full Gitleaks analysis (on master or develop branches) | --verbose |