Packt+ | Advance your knowledge in tech

You're reading from Hands-On Continuous Integration and Delivery Build and release quality software at scale with Jenkins, Travis CI, and CircleCI

Product type Paperback

Published in Aug 2018

Publisher Packt

ISBN-13 9781789130485

Length 416 pages

Edition 1st Edition

Tools

CircleCI

Concepts

Continuous Integration

Author (1):

Belmont

View More author details

Table of Contents (23) Chapters

Title Page

Packt Upsell

Contributors

Preface

1. CI/CD with Automated Testing FREE CHAPTER

2. Basics of Continuous Integration

3. Basics of Continuous Delivery

4. The Business Value of CI/CD

5. Installation and Basics of Jenkins

6. Writing Freestyle Scripts

7. Developing Plugins

8. Building Pipelines with Jenkins

9. Installation and Basics of Travis CI

10. Travis CI CLI Commands and Automation

11. Travis CI UI Logging and Debugging

12. Installation and Basics of CircleCI

13. CircleCI CLI Commands and Automation

14. CircleCI UI Logging and Debugging

15. Best Practices

1. Assessments

2. Other Books You May Enjoy

Leave a review - let other readers know what you think

Index

Travis CI introduction

Travis CI is a hosted and automated solution for CI builds. Travis CI uses an in-application configuration file that uses YAML (http://yaml.org/spec/1.2/spec.html) syntax, which we will go over in more detail later in this chapter. Since Travis CI is hosted in the cloud, it therefore has the advantage that it can quickly be used in other environments and different operating systems without us worrying about setup and installation. This means that Travis CI setup is much faster than Jenkins.

Comparing Travis CI and Jenkins

Jenkins is a self-contained and open source automation server that is customizable and requires setup and configuration at the organization level. Remember, in the Jenkins CI chapters we spent some time installing Jenkins on Windows, Linux, and macOS. We also had the ability to configure Jenkins however we wanted. While this is great for software companies with dedicated teams in operations, DevOps and more, it is not as great for open source projects...