Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Secure Continuous Delivery on Google Cloud

You're reading from  Secure Continuous Delivery on Google Cloud

Product type Book
Published in Apr 2024
Publisher Packt
ISBN-13 9781805129288
Pages 304 pages
Edition 1st Edition
Languages
Concepts
Authors (3):
Giovanni Galloro Giovanni Galloro
Profile icon Giovanni Galloro
Nathaniel Avery Nathaniel Avery
Profile icon Nathaniel Avery
David Dorbin David Dorbin
Profile icon David Dorbin
View More author details

Table of Contents (19) Chapters

Preface 1. Part 1:Introduction and Code Your Application
2. Chapter 1: Introducing Continuous Delivery and Software Supply Chain Security 3. Chapter 2: Using Skaffold for Development, Build, and Deploy 4. Chapter 3: Developing and Testing with Cloud Code 5. Chapter 4: Securing Your Code with Cloud Workstations 6. Part 2: Build and Package Your Application
7. Chapter 5: Automating Continuous Integration with Cloud Build 8. Chapter 6: Securely Store Your Software on Artifact Registry 9. Part 3: Deploy and Run Your Application
10. Chapter 7: Exploring Runtimes – GKE, GKE Enterprise, and Cloud Run 11. Chapter 8: Automating Software Delivery Using Cloud Deploy 12. Chapter 9: Securing Your Runtimes with Binary Authorization 13. Part 4: Hands-On Secure Pipeline Delivery and Looking Forward
14. Chapter 10: Demonstrating an End-to-End Software Delivery Pipeline 15. Chapter 11: Integrating with Your Organization’s Workflows 16. Chapter 12: Diving into Best Practices and Trends in Continuous Delivery 17. Index 18. Other Books You May Enjoy

Integrating Cloud Deploy with automated testing

Automated testing is an important part of a source-to-prod workflow. You can use deployment verification after any completed deployment to confirm that your deployment works as expected.

In addition to deployment verification, you can use deploy hooks to reach out to local or remote resources. Sometimes, you need to connect to a third-party service after deployment has been completed. Post-deploy hooks make that possible. As with verification, post-deploy hooks run from a user-defined container. Unlike verification, deploy hooks are intended for actions that only have an effect when they’re run for the first time, for a given release.

In the example in this section, the delivery pipeline uses a post-deploy hook to call an API from the Google PageSpeed Insights (PSI) tool. PSI assesses your website’s user experience across mobile and desktop environments while also providing suggestions to improve performance. This...

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}