--- version: 2.1 orbs: prometheus: prometheus/prometheus@0.8.0 go: circleci/go@0.2.0 jobs: test_frontend: # We need to use a machine executor because the front-end validation runs # containers with mounted volumes which isn't supported with the docker # executor (even with setup_remote_docker). machine: true steps: - checkout - run: sudo service docker restart - run: name: Remove existing Go installation command: sudo rm -rf /usr/local/go # Whenever the Go version is updated here, .promu.yml should also be updated. - go/install: version: "1.14" - run: name: Remove generated code command: make clean - run: name: Generate front-end code command: make all working_directory: ~/project/ui/app environment: JUNIT_DIR: ~/test-results - run: name: Generate assets command: make assets - run: name: Generate API v2 code command: make apiv2 - run: git diff --exit-code - store_test_results: path: ~/test-results test: docker: # Whenever the Go version is updated here, .promu.yml should also be updated. - image: circleci/golang:1.14 # maildev containers are for running the email tests against a "real" SMTP server. # See notify/email_test.go for details. - image: djfarrelly/maildev@sha256:624e0ec781e11c3531da83d9448f5861f258ee008c1b2da63b3248bfd680acfa name: maildev-noauth entrypoint: bin/maildev command: - -v - image: djfarrelly/maildev@sha256:624e0ec781e11c3531da83d9448f5861f258ee008c1b2da63b3248bfd680acfa name: maildev-auth entrypoint: bin/maildev command: - -v - --incoming-user - user - --incoming-pass - pass environment: EMAIL_NO_AUTH_CONFIG: /tmp/smtp_no_auth.yml EMAIL_AUTH_CONFIG: /tmp/smtp_auth.yml steps: - prometheus/setup_environment - go/load-cache: key: v1-go-mod - run: command: | cat \< $EMAIL_NO_AUTH_CONFIG smarthost: maildev-noauth:1025 server: http://maildev-noauth:1080/ EOF cat \< $EMAIL_AUTH_CONFIG smarthost: maildev-auth:1025 server: http://maildev-auth:1080/ username: user password: pass EOF - run: command: make environment: # By default Go uses GOMAXPROCS but a Circle CI executor has many # cores (> 30) while the CPU and RAM resources are throttled. If we # don't limit this to the number of allocated cores, the job is # likely to get OOMed and killed. GOOPTS: "-p 2" - prometheus/check_proto: version: "3.11.4" - prometheus/store_artifact: file: alertmanager - prometheus/store_artifact: file: amtool - go/save-cache: key: v1-go-mod - store_test_results: path: test-results workflows: version: 2 alertmanager: jobs: - test_frontend: filters: tags: only: /.*/ - test: filters: tags: only: /.*/ - prometheus/build: name: build filters: tags: only: /.*/ - prometheus/publish_master: context: org-context requires: - test_frontend - test - build filters: branches: only: master - prometheus/publish_release: context: org-context requires: - test_frontend - test - build filters: tags: only: /^v[0-9]+(\.[0-9]+){2}(-.+|[^-.]*)$/ branches: ignore: /.*/