When you create an agent Pool in Azure DevOps to run your pipeline, you can require each pipeline to be authorized to run on that agent and sometimes this can generate some glitch.
Pipeline decorators are really powerful, but for some users they are a tool too blunt to use. Learn how to run decorator conditionally for an optimal experience
Visual Studio Code + GitHub Codespaces + Hugo = a great combination to write blog post
I cannot stress enough how important are backups and Azure DevOps Server is not an exception, especially because if you do not schedule backups you can have surprises.
Running custom code check during Pull Requests can help to improve quality of code, let's see how you can run some custom checks with Aure DevOps pipeline.
If you need to have a unique incremental number for each pipeline run, Counters are your solution
If you have pipeline run stuck in queue and some of the pool agent are in idle, if you wonder why those agents did not pick the pipeline, the answer is probably some demands.
Suppose you just upgraded your Azure DevOps Server and during the upgrade procedure the wizard tells you that some prerequisites are missing (like sql server version) how should you proceed?
If you want to export all of your Work Items in another format (excel, internal database) Azure DevOps Api are the solution
When you use interactive login for Azure DevOps API you need to check if the user is correctly logged