luxolus/open-nomad
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity
open-nomad/.circleci/config/workflows/build-test.yml

97 lines
2.8 KiB
YAML
Raw Normal View History

Refactor circleci CI scripts This adopts pattern used by Vault, where we split CircleCI yaml config into multiple files that get packed and translated to 2.0. This has two motivations: First, to ease translating config to CircleCI 2.0 so it can run on Enterprise private repository. Second and most importantly, it also adding Enterprise specific jobs in separate files with reduced config file merging conflict resolution.
2019-11-20 16:11:28 +00:00
jobs:
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- build-binaries:
# almost always build binaries as they may be needed
# for e2e tests
filters:
branches:
ignore:
- stable-website
- /^.-ui\b.*/
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- lint-go:
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
# check branches are almost all the backend branches
filters: &backend_check_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
branches:
ignore:
- /^.-ui\b.*/
- /^docs-.*/
- stable-website
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
# Note: comment-out this job in ENT
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- build-darwin-binaries:
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_check_branches_filter
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
- test-e2e:
filters: *backend_check_branches_filter
- test-ui:
filters:
branches:
ignore:
- stable-website
- /^docs-.*/
ci: don't run UI tests for e2e branches (#8956)
2020-09-24 12:59:56 +00:00
- /^e2e-.*/
ci: build darwin on CI build darwin binaries in CI as a basic check. Protects against cross compile issues.
2020-03-23 15:28:54 +00:00
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
# Note: comment-out this job in ENT
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
- test-windows:
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
filters:
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
branches:
ignore:
- /^.-ui\b.*/
- /^docs-.*/
- /^e2e-.*/
- stable-website
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-client"
test_packages: "./client/..."
ci: reduce merge conflict potential in CircleCI config (#8951) We currently have two jobs commented out in ENT because we don't have the test target configured there. So having the filter attached to one of those jobs means changes to filters always create a merge conflict.
2020-09-23 13:35:23 +00:00
# test branches are the branches that can impact unit tests
filters: &backend_test_branches_filter
branches:
ignore:
- /^.-ui\b.*/
- /^docs-.*/
- /^e2e-.*/
- stable-website
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-nomad"
test_packages: "./nomad/..."
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
# API Tests run in a VM rather than container due to the FS tests
# requiring `mount` priviliges.
name: "test-api"
deps: Switch to Go modules for dependency management This PR switches the Nomad repository from using govendor to Go modules for managing dependencies. Aspects of the Nomad workflow remain pretty much the same. The usual Makefile targets should continue to work as they always did. The API submodule simply defers to the parent Nomad version on the repository, keeping the semantics of API versioning that currently exists.
2020-05-30 14:29:47 +00:00
test_module: "api"
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-container:
name: "test-devices"
test_packages: "./devices/..."
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-other"
ci: make split between e2e and integration tests explicit (#9091) Currently we compile (but don't run) the e2e tests as part of `test-other`, which is skipped for branches named `e2e-*`. Move this check into the `test-e2e` job. Split out the vault compatibility integration check as its own makefile target for clarity.
2020-10-14 18:53:21 +00:00
exclude_packages: "./api|./client|./drivers/docker|./drivers/exec|./drivers/shared/executor|./nomad|./devices|./e2e"
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-docker"
test_packages: "./drivers/docker"
# docker is misbehaving in docker-machine-recent image
# and we get unexpected failures
# e.g. https://circleci.com/gh/hashicorp/nomad/3854
executor: go-machine
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-exec"
test_packages: "./drivers/exec"
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-shared-exec"
test_packages: "./drivers/shared/executor"
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Move appveyor tests to circle
2020-05-04 23:02:15 +00:00
- test-machine:
name: "test-32bit"
# Currently we only explicitly test fingerprinting on 32bit
# architectures.
test_packages: "./client/fingerprint"
goarch: "386"
ci: exclude unit test runs from e2e branches (#8909) Branches for the e2e code base can't have impact on the unit tests, so running those tests just extends the time it takes to ship e2e updates. This changeset updates the CircleCI config so that e2e branches run linting, build the binary, and run the e2e unit tests (currently just vault compatibility).
2020-09-18 13:25:29 +00:00
filters: *backend_test_branches_filter
Reference in a new issue Copy permalink