Azure DevOps Scenario related Questions of Different Feature's in Azure DevOps Project
Issue with Repo's.
Scenario 1:
You are facing some challenges with the code in the PROD Environment only.
But the similar issue didn't appear in any of the pre-prod Environment .(DEV/QA/UATETC)
But the team observed that there are some parameters disturbing the application in PROD Environment .& the debugging team identified there was an issue with one of the commit that was part of a PR.
What happened here is the associated branch(source) got deleted after the PR is completed.
Now the product owner/tech delivery lead wants to know below details
Questions in order to resolve the issue:
Who created the feature branch?
When it was created?
What was the last commit ID that was associated with the base branch before the feature branch created?
What are the different modifications that was happened to the associated commit which is causing the issue?
Who created the commit and who authorized the commit?
When the feature branch got deleted after the PR is completed, issue caused commit ID & associated changes got merged into destination branch or not?
What is the procedure to be followed in order to resolve the issue facing with this commit ID?
Questions related to Strategy Implementation:
In-order to ensure the best practices are implemented in the DEVOPS culture:
What kind of security measures need to be taken care in order to make sure that these kind of issues wont repeat?
What kind of policy management we need to implement in order to make sure that these kind of issues wont repeat?
Does the implemented branch strategy, branch policy, branch security measures are as per the standards or not?
Any deviations that were implemented earlier to be corrected in the existing scenario
Any kind of observations to be monitored or diagnosed at the project level or repo level or branch level?
Caution while working with PowerShell Task in Azure DevOps Pipelines when trying to check out the file path from a repo:
Actual parameters should be associated with binding parameters and binding parameters should be associated with pipeline variables
Comments
Post a Comment