Book Image

Hands-On Continuous Integration and Delivery

By : Jean-Marcel Belmont
Book Image

Hands-On Continuous Integration and Delivery

By: Jean-Marcel Belmont

Overview of this book

Hands-On Continuous Integration and Delivery starts with the fundamentals of continuous integration (CI) and continuous delivery (CD) and where it fits in the DevOps ecosystem. You will explore the importance of stakeholder collaboration as part of CI/CD. As you make your way through the chapters, you will get to grips with Jenkins UI, and learn to install Jenkins on different platforms, add plugins, and write freestyle scripts. Next, you will gain hands-on experience of developing plugins with Jenkins UI, building the Jenkins 2.0 pipeline, and performing Docker integration. In the concluding chapters, you will install Travis CI and Circle CI and carry out scripting, logging, and debugging, helping you to acquire a broad knowledge of CI/CD with Travis CI and CircleCI. By the end of this book, you will have a detailed understanding of best practices for CI/CD systems and be able to implement them with confidence.
Table of Contents (18 chapters)

Chapter 14: Circle CI UI Logging and Debugging

  1. The API Endpoint was POST https://circleci.com/api/v1.1/project/:vcs-type/:username/:project/follow?circle-token=:token.
  2. Yes the cat utility can be used to create new files you can do the following:
cat > somefile
# input
input
Press Control D
  1. You would use the vertical Pipe operator (|) to create a multi-line command like this for example:
- run:
name: Run Tests and Run Code Coverage with NYC
command: |
echo "Generate Code Coverage"
npm test
echo "Show the coverage"
npm run coverage
# or simply
- run: |
echo "Generate Code Coverage"
npm test
echo "Show the coverage"
npm run coverage

  1. Yes if you run the set -x option in a script and are setting secrets they may leak into standard output so instead store secrets or keys in project or context settings...