Member-only story
DevSecOps Service-Web Hook Based Customization
Basically, it will be a case that includes DevSecOps practices in an integrated manner with sast structure by using git version management flexibly. Management and continuous integration of a git-based commit or pull request state on Azure DevOps will be provided with a case in which the following structures are used:
- Azure Devops Service Hook
- Azure DevOps Api
- Sonarcloud Webhook
- Azure functions
When merge requests are created directly in Azure DevOps, a dependency feature can be added to the approvals to perform the merge process. The most interesting of these approval dependencies may be the requirement to pass the specified pipeline. Looking at this feature, it seems likely to provide many benefits. But it has a somewhat strange logic. If the target branch has already passed the specified pipeline, approval is provided. Although this does not seem logically very understandable to me, the explanation of this logic afterwards is “Only if the desired pipeline controls work for the target, the target is seen as updatable.” It was made in the form.
In other words, if you do not have a target branch registered with the “clean” pipeline, there are not enough criteria for merge. Instead of “not polluting the clean building”, which is my…
