Subscription

Explore Products

Best Sellers

New Releases

Books

Videos

Audiobooks

Learning Hub

Conferences

Free Learning

You're reading from Implementing Azure DevOps Solutions Learn about Azure DevOps Services to successfully apply DevOps strategies

Product type Paperback

Published in Jun 2020

Publisher Packt

ISBN-13 9781789619690

Length 432 pages

Edition 1st Edition

Tools

Azure

Concepts

DevOps

Authors (2):

Henry Been

Maik van der Gaag

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: Getting to Continuous Delivery

2. Introduction to DevOps FREE CHAPTER

3. Everything Starts with Source Control

4. Moving to Continuous Integration

5. Continuous Deployment

6. Section 2: Expanding your DevOps Pipeline

7. Dependency Management

8. Infrastructure and Configuration as Code

9. Dealing with Databases in DevOps Scenarios

10. Continuous Testing

11. Security and Compliance

12. Section 3: Closing the Loop

13. Application Monitoring

14. Gathering User Feedback

15. Section 4: Advanced Topics

16. Containers

17. Planning Your Azure DevOps Organization

18. AZ-400 Mock Exam

19. Assessments

20. Other Books You May Enjoy

Leave a review - let other readers know what you think

Chapter 2

The main difference between centralized and decentralized source control is that in a decentralized source control system, every user of the system has the full history of the sources. In a centralized system, only the server has the full history. Decentralized systems work best when working disconnected from the server, whereas centralized systems often allow for more detailed access control.
True. Git is the best known decentralized source control system.
The correct answer is number 3. Rebasing is not a branching strategy, but a merging strategy.

When working with Git, a pull request is used to request the merging of changes from one branch with another. Pull requests can be reviewed, approved, or denied. To enforce the use of pull requests, Git policies can be used.
The correct answer is number 2. Trunk-based development is not a merging strategy, but a branching...

The rest of the chapter is locked

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

Start free trial

Renews at €18.99/month. Cancel anytime

Authors (2)

Been

Henry Been has been working in IT for over ten years. He is an independent architect, developer, and trainer in a number of companies. With many of these companies, he has embarked on a journey implementing practices such as continuous integration and deployment, infrastructure as code, trunk-based development, and implementing feedback loops. Alongside his work, he creates online training courses for A Cloud Guru, and frequently speaks at meetups and conferences. He was awarded the Microsoft MVP award in 2019.

See other products by Been

Gaag

Maik van der Gaag is an architect and trainer at 3fifty, an experienced consultancy company with a strong focus on the Microsoft cloud. He has over 15 years' experience of providing architecture, development, training, and design expertise. During his career, he has worked on a variety of projects, ranging from cloud transformations to DevOps implementations. He loves to share his knowledge, which was also one of the reasons why he founded the Dutch Cloud meetup. Maik is a public speaker, writes blogs, and organizes events.

See other products by Gaag