Page History
...
The CircleCI configuration file .circleci/config.ym
l contains the definition of the build steps, including running the automated tests and submitting the results.
Code Block | ||||
---|---|---|---|---|
| ||||
version: 2 # use CircleCI 2.0 jobs: # a collection of steps build: # runs not using Workflows must have a `build` job as entry point working_directory: ~/demo/java-junit-calc # directory where steps will run docker: # run the steps with Docker - image: circleci/openjdk:8-jdk-browsers # ...with this image as the primary container; this is where all `steps` will run steps: # a collection of executable commands - checkout: # check out source code to working directory path: ~/demo - restore_cache: # restore the saved cache after the first run or if `pom.xml` has changed key: circleci-java-junit-calc-demo # circleci-java-junit-calc-demo-{{ checksum "pom.xml" }} - run: mvn dependency:go-offline # gets the project dependencies - run: mvn test # run the actual tests - save_cache: # saves the project dependencies paths: - ~/.m2 key: circleci-java-junit-calc-demo # circleci-java-junit-calc-demo-{{ checksum "pom.xml" }} - store_test_results: # uploads the test metadata from the `target/surefire-reports` directory so that it can show up in the CircleCI dashboard. path: target/surefire-reports - run: 'curl -H "Content-Type: multipart/form-data" -u $jira_user:$jira_password -F "file=@target/surefire-reports/TEST-com.xpand.java.CalcTest.xml" "$jira_server_url/rest/raven/1.0/import/execution/junit?projectKey=CALC"' |
...
We're using "curl" utility that comes in Unix based OS'es but you can easily use another tool to make the HTTP request; however, "curl" is provided in the container used by CircleCI.
|
References