# uncomment and uses to customize/extend the configuration here if needed
# (it needs to be at the same level than "- project")
# - ".gitlab-ci-extended.yml"
-project:"open-source/gitlab-ci-templates"
ref:"branch/default"
file:
-"templates/no-duplicated-ci-pipelines.yml"# use workflow to avoid duplicated pipelines
-"templates/lint/flake8.yml"# will do the equivalent of 'tox -e flake8'
-"templates/lint/check-manifest.yml"# will do the equivalent of 'tox -e check-manifest'
-"templates/lint/yamllint.yml"# will do the equivalent of 'tox -e yamllint'
-"templates/tests/py3.yml"# will do the equivalent of 'tox -e py3'
-"templates/build-debian-package.yml"# will build a .deb and upload it to heptapod files
-"templates/create-release-on-heptapod-including-debian-package.yml"# this will create a release on heptapod AND uses uploaded .deb by build-debian-package
-"templates/upload-to-pypi.yml"# on a new mercurial tag (expected to be done with release-new), will push a release on pypi
stages:
-lint
-tests
...
...
@@ -12,60 +20,8 @@
stages:
-lint
-tests
-after-tests
before_script:
-pip install tox
flake8:
stage:lint
script:tox -e flake8
check-manifest:
stage:lint
script:tox -e check-manifest
black:
stage:lint
script:tox -e black
yamllint:
rules:
-changes:
-"**/*.yaml"
-"**/*.yml"
stage:lint
before_script:
-pip install tox
script:
-tox -e yamllint
# If you have mypy set up
# mypy:
# stage: lint
# script: tox -e mypy
py3:
stage:tests
script:tox -e py3
# If you have your project on readthedocs, you can automatically trigger its
# build by setting:
# - READTHEDOCS_TOKEN
# - READTHEDOCS_ID
# in your heptapod project Settings > CI/CD > Variables.
# You can find those secrets by creating a new integration in your readthedocs