azure pipelines
From time to time, there is a need to touch git repository from the pipeline - push tag, push commit with release notes, whatever your process need. To properly configure such functionality, you have to: * explicitly mark that pipeline must persists git authentication after repository checkout: jobs: - job: myJob
azure devops
For better readability, it is nice to break the lines in bigger conditions in Azure DevOps Pipeline definition, but it is not clearly documented, how it should be done exactly. Below you will find three examples. Conditional template inclusion jobs: - job: myJob displayName: 'My fancy job' steps:
azure pipelines
Azure Pipelines provides possibility to trigger stages manually by setting the flag in the stage definition like it is described in the below documentation: Stages in Azure Pipelines - Azure PipelinesLearn how to organize your jobs into stages, define dependencies, and set conditions. Understand how to implement deployment strategies and
git
You are starting working on a new branch. You want to push some commit and you get such message: $ git push fatal: The current branch feature/my-branch has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin feature/my-branch Again,
bicep
Sometimes you need to define nullable parameters in Bicep files. It is possible by adding ? character after the type of the parameter: param <param_name> <param_type>? For example - let's assume the case that you need to deploy subnet and assign the NSG