You're reading from Atlassian DevOps Toolchain Cookbook Recipes for building, automating, and managing applications with Jira, Bitbucket Pipelines, and more

Product type Paperback

Published in Jul 2024

Publisher Packt

ISBN-13 9781835463789

Length 504 pages

Edition 1st Edition

Languages

Python

Tools

Atlassian Confluence

Concepts

DevOps

Authors (4):

Rodney Nissen

Robert Wen

Alex Ortiz

Edward Gaile

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1:Beginning the Cycle FREE CHAPTER

2. Chapter 1: An Introduction to DevOps and the Atlassian Ecosystem

3. Chapter 2: Discovering Customer Needs with Jira Product Discovery

4. Chapter 3: Planning and Documentation with Confluence

5. Part 2: Development to Deployment

6. Chapter 4: Enabling Connections for Design, Source Control, and Continuous Integration

7. Chapter 5: Understanding Bitbucket and Bitbucket Pipelines

8. Chapter 6: Extending and Executing Bitbucket Pipelines

9. Chapter 7: Leveraging Test Case Management and Security Tools for DevSecOps

10. Chapter 8: Deploying with Bitbucket Pipelines

11. Chapter 9: Leveraging Docker and Kubernetes for Advanced Configurations

12. Part 3: Maintaining Operations

13. Chapter 10: Collaborating with Operations through Continuous Deployment and Observability

14. Chapter 11: Monitoring Component Activity and Metrics Through CheckOps in Compass

15. Chapter 12: Escalate Using Opsgenie Alerts

16. Part 4: Putting It into Practice

17. Chapter 13: Putting It All Together with a Real-World Example

18. Chapter 14: Appendix – Key Takeaways and the Future of Atlassian DevOps Tools

19. Index

Why subscribe?

20. Other Books You May Enjoy

Understanding pull requests and merging best practices

Tracking branches and changes to your code is only one of the features built into Bitbucket. When you are finished with your code changes, those changes need to be merged back to the branch that is upstream from your current branch. If you are following the Gitflow model, then that means that all of your code changes were done in a dedicated feature branch and now it is time to merge those changes back into the develop branch. The process of doing this merge is called a pull request. A pull request is more than just merging your code changes. The rest of this recipe will explain and walk you through how to use pull requests to maintain high-quality code and minimize the chances that your new code changes will break something.

How to do it…

Once you are done with your changes, it is time to initiate a pull request. This pull request will trigger a chain reaction of events that is covered in the following steps:

...