Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Continuous Integration and Delivery

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

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781789130485
Length 416 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jean-Marcel Belmont Jean-Marcel Belmont
Author Profile Icon Jean-Marcel Belmont
Jean-Marcel Belmont
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

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 16. Assessments 17. Other Books You May Enjoy

Chapter 11: Travis CI UI Logging and Debugging

  1. Yes whenever you merge a pull request in GitHub, Travis CI will automatically kick off another build.
  2. No it doesn't, but you will see labels for the before_install and install lifecycle events as well as some other lifecycle events.
  3. You will need to use Docker to pull down an image and you can find the full list of Docker images here (https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image).
  4. Yes, but you will need to email [email protected] and then request whatever specific repositories you want to have debug mode enabled for. Additionally you will need to make a call to Travis API with the corresponding job id to trigger a build in debug mode.
  5. You will need to make an API call to the Travis API by doing a GET request to the /builds endpoint. Here is a sample request using the curl...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image