Bicep is a language for declaratively deploying Azure resources. You can use Bicep instead of JSON for developing your Azure Resource Manager templates (ARM templates). Bicep simplifies the developing process by providing shorter syntax and really nice intellisense support for Visual Studio Code.
Bicep is based on “.bicep” files that are written with Visual Studio Code (or any other text editor, but I recommend to use the Code). If Bicep …
In the last blog post we looked how we can manually create work items into Azure DevOps from Application Insights. Manual labor is something that we want to avoid in DevOps world, so let’s take a look how we can automatically create bug type of work item into Azure DevOps when error is detected in Application Insights. The guide seems quite long, but actually you can do it in 15 …
Application Insights can be integrated into Azure DevOps, so that developers can create bug work items directly from Application Insights without copy-pasting any of the exception details.
First we need to integrate our Application Insights instance with our DevOps instance. This is done through Azure Portal Application Insights settings Work Items
URL is the root url of your Azure DevOps project. For example https://dev.azure.com/OrganizationX
Project of course defines where the …
Azure CDN is relatively new service (GA release was near the end of 2018) that allows users to share their static web site content globally, so that the site resources are close to web site users. CDN lifts network usage from the web server, which helps to scale the service. Like many other Azure services, the CDN pricing is based on usage and does not contain any upfront costs.
Every now and then I’m asked to do a Work Item migration from one Azure DevOps organization (or project) to another and as it is not that rare case anymore, it is still surprisingly hard to do and there are few good reasons why.
The most common problem with migration is that, the source data is not integrated. It has lots of special cases and edges that …
Boards is the joining force of the Azure DevOps work items. It contains four different views for work items (well five if you count queries) and they are all suitable for different purposes. In this post I’m going to show you the main differences between work items, boards, backlogs and sprint views.
On top of the menu is Work Items. Work items view is good for finding …
Azure DevOps has multiple ready made work item types, and they are usually more than enough to run normal agile software development. In this post I will cover what are the regular work item types and how they should be used.
By default Azure DevOps has four tiers of work items: Epic, Feature, User Story and Task/Bug. Bug can be configured to be in User Story level or in …
Work items are way to track work progress in Azure DevOps. They tell you what the team is currently working on, what is finished and what job is still to do. That’s it. OK in real world it is not that easy, because you have different kind of work to do, tickets are moving back and forth between being closed and active etc. To tackle all this chaos, I will …
Today I was setting up a self-hosted agent, that could run Robot framework tests. I wanted the agent to run robot tests and push results into Azure DevOps as a test result of release run. First my releases returned weird looking return codes like ##[error]Bash exited with code ‘8’. Robot framework documentation says that runner returns following return codes:
| RC | Explanation |
|---|---|
| 0 | All critical tests passed. |
| 1-249 | Returned number |
Today I listened a great podcast episode Episode 400: Michaela Greiler on Code Reviews, where Michaela Greiler talks about how to do great code reviews. I have to say, that I love this topic and the tips Michaela gives are so great, that I want to share some of them with you.
First thought of code reviews is usually, that they are …