Mirrors
/
synapse-old
mirror of https://github.com/matrix-org/synapse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
synapse-old/.circleci/config.yml

34 lines
1.2 KiB
YAML
Raw Normal View History

Dockerised sytest (#3660)
2018-08-14 05:30:34 -06:00
version: 2
jobs:
Make a ":latest" tag, and a SHA1 commit ID one too. Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".
2018-09-27 04:44:21 -06:00
dockerhubuploadrelease:
Build and push docker image to hub
2018-09-25 02:43:21 -06:00
machine: true
steps:
- checkout
Update docker image to use Python 3.7. (#5546) Python 3.7 is apparently faster than 3.6, and should be mature enough.
2019-06-24 22:20:53 -06:00
- run: docker build -f docker/Dockerfile --label gitsha1=${CIRCLE_SHA1} -t matrixdotorg/synapse:${CIRCLE_TAG} -t matrixdotorg/synapse:${CIRCLE_TAG}-py3 .
Make username configurable in the UI too
2018-09-25 03:29:38 -06:00
- run: docker login --username $DOCKER_HUB_USERNAME --password $DOCKER_HUB_PASSWORD
build python 3 docker images on circle CI (#3976)
2018-09-28 05:36:35 -06:00
- run: docker push matrixdotorg/synapse:${CIRCLE_TAG}
- run: docker push matrixdotorg/synapse:${CIRCLE_TAG}-py3
Make a ":latest" tag, and a SHA1 commit ID one too. Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".
2018-09-27 04:44:21 -06:00
dockerhubuploadlatest:
machine: true
steps:
- checkout
Update docker image to use Python 3.7. (#5546) Python 3.7 is apparently faster than 3.6, and should be mature enough.
2019-06-24 22:20:53 -06:00
- run: docker build -f docker/Dockerfile --label gitsha1=${CIRCLE_SHA1} -t matrixdotorg/synapse:latest -t matrixdotorg/synapse:latest-py3 .
Make a ":latest" tag, and a SHA1 commit ID one too. Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".
2018-09-27 04:44:21 -06:00
- run: docker login --username $DOCKER_HUB_USERNAME --password $DOCKER_HUB_PASSWORD
- run: docker push matrixdotorg/synapse:latest
build python 3 docker images on circle CI (#3976)
2018-09-28 05:36:35 -06:00
- run: docker push matrixdotorg/synapse:latest-py3
Add JUnit summaries to CircleCI as well as merged runs (#3704)
2018-09-12 07:29:21 -06:00
Dockerised sytest (#3660)
2018-08-14 05:30:34 -06:00
workflows:
version: 2
build:
jobs:
Make a ":latest" tag, and a SHA1 commit ID one too. Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".
2018-09-27 04:44:21 -06:00
- dockerhubuploadrelease:
Build and push docker image to hub
2018-09-25 02:43:21 -06:00
filters:
tags:
Docker build all tags starting vX.Y.Z, inc RCs Note the regex must match the complete string anyway, so the leading ^ was useless.
2018-10-03 04:52:05 -06:00
only: /v[0-9].[0-9]+.[0-9]+.*/
Also, don't run this job on any branches
2018-09-25 03:37:08 -06:00
branches:
ignore: /.*/
Make a ":latest" tag, and a SHA1 commit ID one too. Latest is horrible and makes debugging what has happened anywhere a nightmare. We push a latest because of demand for it, but we'll also push a SHA1 commit id so those wanting to know what they're running (and be able to roll back if required) can use those instead. Note that latest here is defined as "most recent master commit" not "most recent released version", as the actual semantics of making latest correct while still being able to build bugfixed releases of previous versions is just ARGH. So we define it as "master" not "latest release".
2018-09-27 04:44:21 -06:00
- dockerhubuploadlatest:
filters:
branches:
only: master