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
Continuous Delivery with Docker and Jenkins

You're reading from   Continuous Delivery with Docker and Jenkins Create secure applications by building complete CI/CD pipelines

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781838552183
Length 350 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Rafał Leszko Rafał Leszko
Author Profile Icon Rafał Leszko
Rafał Leszko
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Setting Up the Environment
2. Introducing Continuous Delivery FREE CHAPTER 3. Introducing Docker 4. Configuring Jenkins 5. Section 2: Architecting and Testing an Application
6. Continuous Integration Pipeline 7. Automated Acceptance Testing 8. Clustering with Kubernetes 9. Section 3: Deploying an Application
10. Configuration Management with Ansible 11. Continuous Delivery Pipeline 12. Advanced Continuous Delivery 13. Best practices 14. Assessment 15. Other Books You May Enjoy

Summary

In this chapter, we have completed the Continuous Delivery pipeline and now we can finally release the application. The following are the key takeaways from the chapter:

  • For the purpose of Continuous Delivery, two environments are indispensable: staging and production.
  • Nonfunctional tests are an essential part of the Continuous Delivery process and should always be considered as pipeline stages.
  • Nonfunctional tests that don't fit the Continuous Delivery process should be used as periodic tasks in order to monitor the overall performance trends.
  • Applications should always be versioned; however, the versioning strategy depends on the type of the application.
  • A minimal Continuous Delivery pipeline can be implemented as a sequence of scripts that ends with two stages: release and smoke test.
  • The smoke test should always be added as the last stage of the Continuous Delivery...
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