RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
authelia/.buildkite/pipeline.yml

44 lines
1.1 KiB
YAML
Raw Normal View History

Utilise Buildkite for Authelia CI/CD (#507) Publish steps are currently disabled.
2019-12-27 11:07:53 +00:00
steps:
Build docker image upfront in CI and use it in integration tests. (#555) * Build docker image upfront in CI and use it in integration tests. Previously, the development workflow was broken because the container generated from Dockerfile.CI was used in dev environments but the binary was not pre-built as it is on buildkite. I propose to just remove that image and use the "to be published" image instead in integration tests. This will have several advantages: - Fix the dev workflow. - Remove CI arch from authelia-scripts build command - Optimize CI time in buildkite since we'll cache a way small artifact - We don't build authelia more than once for earch arch. * Fix suites and only build ARM images on master or tagged commits * Optimise pipeline dependencies and Kubernetes suite to utilise cache * Run unit tests and docker image build in parallel. * Fix suite trying to write on read only fs. Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
2020-01-17 19:46:51 +00:00
- label: ":hammer_and_wrench: Unit Test"
Utilise Buildkite for Authelia CI/CD (#507) Publish steps are currently disabled.
2019-12-27 11:07:53 +00:00
command: "authelia-scripts --log-level debug ci"
Add back wait block in buildkite pipeline.
2020-01-17 22:55:02 +00:00
- wait
Utilise Buildkite for Authelia CI/CD (#507) Publish steps are currently disabled.
2019-12-27 11:07:53 +00:00
- label: ":docker: Image Builds"
command: ".buildkite/steps/buildimages.sh | buildkite-agent pipeline upload"
Build static Go binary
2020-01-05 04:12:24 +00:00
agents:
build: "true"
Build docker image upfront in CI and use it in integration tests. (#555) * Build docker image upfront in CI and use it in integration tests. Previously, the development workflow was broken because the container generated from Dockerfile.CI was used in dev environments but the binary was not pre-built as it is on buildkite. I propose to just remove that image and use the "to be published" image instead in integration tests. This will have several advantages: - Fix the dev workflow. - Remove CI arch from authelia-scripts build command - Optimize CI time in buildkite since we'll cache a way small artifact - We don't build authelia more than once for earch arch. * Fix suites and only build ARM images on master or tagged commits * Optimise pipeline dependencies and Kubernetes suite to utilise cache * Run unit tests and docker image build in parallel. * Fix suite trying to write on read only fs. Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
2020-01-17 19:46:51 +00:00
depends_on: ~
- wait
- label: ":chrome: Integration Tests"
command: ".buildkite/steps/e2etests.sh | buildkite-agent pipeline upload"
Utilise Buildkite for Authelia CI/CD (#507) Publish steps are currently disabled.
2019-12-27 11:07:53 +00:00
depends_on:
Build docker image upfront in CI and use it in integration tests. (#555) * Build docker image upfront in CI and use it in integration tests. Previously, the development workflow was broken because the container generated from Dockerfile.CI was used in dev environments but the binary was not pre-built as it is on buildkite. I propose to just remove that image and use the "to be published" image instead in integration tests. This will have several advantages: - Fix the dev workflow. - Remove CI arch from authelia-scripts build command - Optimize CI time in buildkite since we'll cache a way small artifact - We don't build authelia more than once for earch arch. * Fix suites and only build ARM images on master or tagged commits * Optimise pipeline dependencies and Kubernetes suite to utilise cache * Run unit tests and docker image build in parallel. * Fix suite trying to write on read only fs. Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
2020-01-17 19:46:51 +00:00
- "build-docker-amd64"
Utilise Buildkite for Authelia CI/CD (#507) Publish steps are currently disabled.
2019-12-27 11:07:53 +00:00
Remove Travis and promote Buildkite (#545) * Remove Travis and promote Buildkite * Add Docker Size badge to README.md * Call MicroBadger webhook to update metadata for shields Add updateMicroBadger function and refactor publishDockerReadme to be called explicitly instead of on every deployManifest call.
2020-01-16 20:57:44 +00:00
- wait:
if: build.branch == "master" || build.branch =~ /^v/
- label: ":docker: Image Deployments"
command: ".buildkite/steps/deployimages.sh | buildkite-agent pipeline upload"
branches: "master v*"
- wait:
if: build.branch == "master" || build.branch =~ /^v/
- label: ":docker: Deploy Manifests"
command: "authelia-scripts docker push-manifest"
branches: "master v*"
env:
DOCKER_CLI_EXPERIMENTAL: "enabled"
- label: ":github: Deploy Artifacts"
command: ".buildkite/steps/ghartifacts.sh"
agents:
upload: "fast"
Build docker image upfront in CI and use it in integration tests. (#555) * Build docker image upfront in CI and use it in integration tests. Previously, the development workflow was broken because the container generated from Dockerfile.CI was used in dev environments but the binary was not pre-built as it is on buildkite. I propose to just remove that image and use the "to be published" image instead in integration tests. This will have several advantages: - Fix the dev workflow. - Remove CI arch from authelia-scripts build command - Optimize CI time in buildkite since we'll cache a way small artifact - We don't build authelia more than once for earch arch. * Fix suites and only build ARM images on master or tagged commits * Optimise pipeline dependencies and Kubernetes suite to utilise cache * Run unit tests and docker image build in parallel. * Fix suite trying to write on read only fs. Co-authored-by: Amir Zarrinkafsh <nightah@me.com>
2020-01-17 19:46:51 +00:00
depends_on:
- "build-docker-amd64"
- "build-docker-arm32v7"
- "build-docker-arm64v8"
Remove Travis and promote Buildkite (#545) * Remove Travis and promote Buildkite * Add Docker Size badge to README.md * Call MicroBadger webhook to update metadata for shields Add updateMicroBadger function and refactor publishDockerReadme to be called explicitly instead of on every deployManifest call.
2020-01-16 20:57:44 +00:00
if: build.tag != null