EMERGING TRENDS IN SOFTWARE ENGINEERING
DEVOPS
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
One repository per project or microservice
|
|
|
Branches enabled for online patching if needed
|
|
|
One branch per environment (Dev, Qa and Master)
|
|
|
Protected master branch
|
Detailed explanation-1: -You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.
Detailed explanation-2: -Require a minimum number of reviewers. Check for comment resolution. Limit merge types. Build Validation. Status Checks. Automatically Included Reviewers. 26-May-2021
Detailed explanation-3: -Log in to your GitLab instance as an admin. Go to the project you want to protect. Click on Settings. Click on Protected branches. In the dropdown, select the branch you want to protect and click on Protect. You will now see a list of your protected branches.