forked from OpenTelecom/kazoo
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* move circle config to 2.0 location * fail if error log has errors * address concern * echo it then exit
- Loading branch information
1 parent
2f35988
commit a8bbad4
Showing
14 changed files
with
263 additions
and
176 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,125 @@ | ||
| # This configuration was automatically generated from a CircleCI 1.0 config. | ||
| # It should include any build commands you had along with commands that CircleCI | ||
| # inferred from your project structure. We strongly recommend you read all the | ||
| # comments in this file to understand the structure of CircleCI 2.0, as the idiom | ||
| # for configuration has changed substantially in 2.0 to allow arbitrary jobs rather | ||
| # than the prescribed lifecycle of 1.0. In general, we recommend using this generated | ||
| # configuration as a reference rather than using it in production, though in most | ||
| # cases it should duplicate the execution of your original 1.0 config. | ||
| version: 2 | ||
| jobs: | ||
| build: | ||
| working_directory: ~/2600hz/kazoo | ||
| shell: /bin/bash --login | ||
| # CircleCI 2.0 does not support environment variables that refer to each other the same way as 1.0 did. | ||
| # If any of these refer to each other, rewrite them so that they don't or see https://circleci.com/docs/2.0/env-vars/#interpolating-environment-variables-to-set-other-environment-variables . | ||
| environment: | ||
| CIRCLE_ARTIFACTS: /tmp/circleci-artifacts | ||
| CIRCLE_TEST_REPORTS: /tmp/circleci-test-results | ||
| TZ: "/usr/share/zoneinfo/UTC" | ||
| # In CircleCI 1.0 we used a pre-configured image with a large number of languages and other packages. | ||
| # In CircleCI 2.0 you can now specify your own image, or use one of our pre-configured images. | ||
| # The following configuration line tells CircleCI to use the specified docker image as the runtime environment for you job. | ||
| # We have selected a pre-built image that mirrors the build environment we use on | ||
| # the 1.0 platform, but we recommend you choose an image more tailored to the needs | ||
| # of each job. For more information on choosing an image (or alternatively using a | ||
| # VM instead of a container) see https://circleci.com/docs/2.0/executor-types/ | ||
| # To see the list of pre-built images that CircleCI provides for most common languages see | ||
| # https://circleci.com/docs/2.0/circleci-images/ | ||
| docker: | ||
| - image: circleci/build-image:ubuntu-14.04-XXL-upstart-1189-5614f37 | ||
| command: /sbin/init | ||
| - image: couchdb:2.1.1 | ||
| - image: rabbitmq:3.7 | ||
| - image: circleci/python:3.6.1 | ||
|
|
||
| steps: | ||
| # Machine Setup | ||
| # If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each | ||
| # The following `checkout` command checks out your code to your working directory. In 1.0 we did this implicitly. In 2.0 you can choose where in the course of a job your code should be checked out. | ||
| - checkout | ||
| # Prepare for artifact and test results collection equivalent to how it was done on 1.0. | ||
| # In many cases you can simplify this from what is generated here. | ||
| # 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/' | ||
| - run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS | ||
| # This is based on your 1.0 configuration file or project settings | ||
| - run: | ||
| working_directory: ~/2600hz/kazoo | ||
| command: echo -e "export OTP_VERSION=$(<~/2600hz/kazoo/make/erlang_version)\nexport PATH=${HOME}/.kerl/$OTP_VERSION/bin:${PATH}\n" >> $BASH_ENV | ||
| # - run: | ||
| # working_directory: ~/2600hz/kazoo | ||
| # command: 'sudo service rabbitmq-server status || sudo service rabbitmq-server | ||
| # start; sudo docker info >/dev/null 2>&1 || sudo service docker start; ' | ||
| # Dependencies | ||
| # This would typically go in either a build or a build-and-test job when using workflows | ||
| # Restore the dependency cache | ||
| - restore_cache: | ||
| keys: | ||
| # This branch if available | ||
| - v1-dep-{{ .Branch }}- | ||
| # Default branch if not | ||
| - v1-dep-master- | ||
| # Any branch if there are none on the default branch - this should be unnecessary if you have your default branch configured correctly | ||
| - v1-dep- | ||
| # This is based on your 1.0 configuration file or project settings | ||
| - run: echo -e "\n. ~/.kerl/$OTP_VERSION/activate\n" >> $BASH_ENV | ||
| - run: | ||
| command: bash ./scripts/circleci-build-erlang.sh | ||
| no_output_timeout: 1800s | ||
| - run: which ag >/dev/null 2>&1 || sudo apt-get update; sudo apt-get install silversearcher-ag | ||
| - run: sudo pip install --upgrade pip | ||
| - run: sudo pip install PyYAML mkdocs pyembed-markdown jsonschema | ||
| # Save dependency cache | ||
| - save_cache: | ||
| key: v1-dep-{{ .Branch }}-{{ epoch }} | ||
| paths: | ||
| # These cache paths were specified in the 1.0 config | ||
| - ~/.kerl | ||
| - ~/.local/ | ||
| # Test | ||
| # This would typically be a build job when using workflows, possibly combined with build | ||
| # This is based on your 1.0 configuration file or project settings | ||
| - run: echo -e "\nexport CHANGED=\"$(git --no-pager diff --name-only HEAD origin/master -- applications core)\"\nexport CHANGED_SWAGGER=\"$(git --no-pager diff --name-only HEAD origin/master -- applications/crossbar/priv/api/swagger.json)\"\n" >> $BASH_ENV | ||
| - run: echo $CHANGED | ||
| - run: ./scripts/state-of-docs.sh || true | ||
| - run: ./scripts/code_checks.bash $($CHANGED) | ||
| - run: make fmt | ||
| - run: JOBS="2" make | ||
| - run: make code_checks | ||
| - run: make app_applications | ||
| - run: ./scripts/validate-js.sh $($CHANGED) | ||
| - run: make apis | ||
| - run: make docs | ||
| - run: make validate-schemas | ||
| - run: ./scripts/state-of-edoc.escript | ||
| - run: make xref | ||
| - run: make sup_completion | ||
| - run: | | ||
| if [[ ! -z "$($CHANGED)" ]]; then | ||
| make build-plt | ||
| TO_DIALYZE="$(echo $($CHANGED))" make dialyze | ||
| fi | ||
| - run: make elvis | ||
| - run: make build-ci-release | ||
| - run: ${PWD}/scripts/check-unstaged.bash | ||
| - run: KAZOO_CONFIG=${PWD}/rel/ci.config.ini REL="kazoo_apps" ACT="console" NODE_NAME_TYPE="-sname" make release | ||
| - run: | | ||
| if [[ $(grep -c -v -F 'exit with reason shutdown' ${PWD}/_rel/kazoo/log/error.log) -gt 0 ]]; then | ||
| cat ${PWD}/_rel/kazoo/log/error.log | ||
| exit 1 | ||
| fi | ||
| # This is based on your 1.0 configuration file or project settings | ||
| - run: mkdir $CIRCLE_ARTIFACTS/logs | ||
| - run: mv ${PWD}/_rel/kazoo/log/* $CIRCLE_ARTIFACTS/logs/ | ||
| - run: cp ${PWD}/rel/ci.relx.config $CIRCLE_ARTIFACTS/ | ||
| - run: find ${PWD}/_rel/kazoo/releases -name kazoo.rel -exec cp {} $CIRCLE_ARTIFACTS/ \; | ||
| # Teardown | ||
| # If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each | ||
| # Save test results | ||
| - store_test_results: | ||
| path: /tmp/circleci-test-results | ||
| # Save artifacts | ||
| - store_artifacts: | ||
| path: /tmp/circleci-artifacts | ||
| - store_artifacts: | ||
| path: /tmp/circleci-test-results |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.