Running a build using a local config YML script to troubleshoot

Let's say that we want to experiment with storing build artifacts, such as code coverage on a project. At the moment we are generating a coverage report but it is not being saved during the builds for us to view a coverage report. This is a good use case of creating a separate config YML script to test this new functionality. Let's store the coverage artifacts from the circleci-jobs-example (https://github.com/packtci/circleci-jobs-example) project and let's also update the test job to cache the node dependencies, as we learned how to do in the previous section.

Run this command to copy the contents of the .circleci directory and create a new directory in the shell:

cp -r .circleci ...

Get Hands-On Continuous Integration and Delivery now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.