1 # This configuration was automatically generated from a CircleCI 1.0 config.
2 # It should include any build commands you had along with commands that CircleCI
3 # inferred from your project structure. We strongly recommend you read all the
4 # comments in this file to understand the structure of CircleCI 2.0, as the idiom
5 # for configuration has changed substantially in 2.0 to allow arbitrary jobs rather
6 # than the prescribed lifecycle of 1.0. In general, we recommend using this generated
7 # configuration as a reference rather than using it in production, though in most
8 # cases it should duplicate the execution of your original 1.0 config.
12 working_directory: ~/jnethack/jnethack-alpha
14 shell: /bin/bash --login
15 # CircleCI 2.0 does not support environment variables that refer to each other the same way as 1.0 did.
16 # 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 .
18 CIRCLE_ARTIFACTS: /tmp/circleci-artifacts
19 CIRCLE_TEST_REPORTS: /tmp/circleci-test-results
20 # In CircleCI 1.0 we used a pre-configured image with a large number of languages and other packages.
21 # In CircleCI 2.0 you can now specify your own image, or use one of our pre-configured images.
22 # The following configuration line tells CircleCI to use the specified docker image as the runtime environment for you job.
23 # We have selected a pre-built image that mirrors the build environment we use on
24 # the 1.0 platform, but we recommend you choose an image more tailored to the needs
25 # of each job. For more information on choosing an image (or alternatively using a
26 # VM instead of a container) see https://circleci.com/docs/2.0/executor-types/
27 # To see the list of pre-built images that CircleCI provides for most common languages see
28 # https://circleci.com/docs/2.0/circleci-images/
29 # change docker-to-image
31 # - image: circleci/build-image:ubuntu-14.04-XXL-1327-3401d20
36 # 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
37 # 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.
39 # Prepare for artifact and test results collection equivalent to how it was done on 1.0.
40 # In many cases you can simplify this from what is generated here.
41 # 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/'
42 - run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS
44 # This would typically go in either a build or a build-and-test job when using workflows
45 # Restore the dependency cache
48 # This branch if available
49 - v1-dep-{{ .Branch }}-
50 # Default branch if not
52 # Any branch if there are none on the default branch - this should be unnecessary if you have your default branch configured correctly
54 # This is based on your 1.0 configuration file or project settings
55 - run: sudo apt-get update; sudo apt-get install nkf flex bison
56 # Save dependency cache
58 key: v1-dep-{{ .Branch }}-{{ epoch }}
60 # This is a broad list of cache paths to include many possible development environments
61 # You can probably delete some of these entries
71 # This would typically be a build job when using workflows, possibly combined with build
72 # This is based on your 1.0 configuration file or project settings
73 - run: find . -type f |xargs nkf -e --overwrite
74 - run: sh sys/unix/setup.sh sys/unix/hints/linux
75 # This is based on your 1.0 configuration file or project settings
78 # 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
81 path: /tmp/circleci-test-results
84 path: /tmp/circleci-artifacts
86 path: /tmp/circleci-test-results