Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Cloud Foundry for Developers

You're reading from   Cloud Foundry for Developers Deploy, manage, and orchestrate cloud-native applications with ease

Arrow left icon
Product type Paperback
Published in Nov 2017
Publisher Packt
ISBN-13 9781788391443
Length 306 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (3):
Arrow left icon
Rick Farmer Rick Farmer
Author Profile Icon Rick Farmer
Rick Farmer
Rahul Kumar Jain Rahul Kumar Jain
Author Profile Icon Rahul Kumar Jain
Rahul Kumar Jain
 Wu Wu
Author Profile Icon Wu
Wu
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Title Page
Credits
About the Authors
Acknowledgements
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
1. Cloud Foundry Introduction 2. Cloud Foundry CLI and Apps Manager FREE CHAPTER 3. Getting Started with PCF Dev 4. Users, Orgs, Spaces, and Roles 5. Architecting and Building Apps for the Cloud 6. Deploying Apps to Cloud Foundry 7. Microservices and Worker Applications 8. Services and Service Brokers 9. Buildpacks 10. Troubleshooting Applications in Cloud Foundry 11. Continuous Integration and Continuous Deployment

What is continuous integration?


Continuous integration (CI) is a practice that developers adopt to maintain their codebase in one shared repository, and they continue to develop and integrate their code in one development branch. The developers work off the development branch, and continuously commit their changes into the development branch, and so prevent the code from going stale over the period. This practice also means developers don't have to worry about code conflicts.

In earlier days, developers used to work on a feature in isolation and used to integrate their features at the end of the development cycle. This used to pose a huge risk of running into code conflicts, or features not working due to interfaces changes, and so on. CI of the code minimizes these risks, and hence the code quality goes up.

Also, with CI in place, the manual process of integration testing is reduced, as all the integration testing is automated at this point.

The developers build new features and commit them...

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 $15.99/month. Cancel anytime
Visually different images