My sandbox for experimenting with CI services
APACHE-2.0 License
My sandbox for experimenting with CI services.
CircleCI | TravisCI | Appveyor | Azure Pipelines | |
---|---|---|---|---|
Build Status |
notifications:
- provider: Email
on_build_success: false
on_build_failure: false
on_build_status_changed: false
The email notification settings are controlled by the user.
notifications:
email: false
deploy-master
: associated with master
branchdeploy-release
: associated with a tag regular expression: /v[0-9]+\.[0-9]+\.[0-9]+/
. See also Git Tag Job Execution.Each jobs depend on all other pythonXY
jobs.
workflows:
version: 2
test-package-publish:
jobs:
[...]
- deploy-master:
requires:
- python27
- python35
- python36
- python37
filters:
branches:
only: master
- deploy-release:
requires:
- python27
- python35
- python36
- python37
filters:
tags:
only: /[0-9]+(\.[0-9]+)*/
branches:
ignore: /.*/
Submission when master
is updated:
Submission when a tag is pushed:
Two sections:
nightly
: associated with master
branchrelease
: associated with a tag regular expression: /v[0-9]+\.[0-9]+\.[0-9]+/
deployment:
nightly:
branch: master
owner: jcfr
commands:
- echo "deployment-nightly"
release:
tag: /v[0-9]+\.[0-9]+\.[0-9]+/
owner: jcfr
commands:
- echo "deployment-release"
Submission when master
is updated:
Submission after creating and pushing a tag:
git tag -s -m "v0.1.0" v0.1.0
git push origin v0.1.0
works as expected:
deploy:
- provider: script
script: echo "deployment-release"
skip_cleanup: true
on:
repo: jcfr/ci-sandbox
tags: true
- provider: script
script: echo "deployment-nightly"
skip_cleanup: true
on:
repo: jcfr/ci-sandbox
branch: master
Here is a submission associated with master
: