This post is the first of a large series of blog posts on DevOps on Azure, I will expose my current experience for the implementation of a DevOps process with Terraform, Ansible, VSTS, Inspec, Jenkins, …..

The objective of this series is not to rewrite existing documentation, posts, articles, … but it will be a “cookbook” type series with posts that will expose real uses cases with best practice of use of these tools in enterprises.

To start, I’ll talk about Terraform and how to use it to provision resources in Azure (also valid for other cloud providers).

Read More

In this article I want to expose a problem (and a solution) that I encountered in my customer that use TFS 2018.2

The problem

The client reported the following problem to me: since he upgrade from TFS 2018.0 to TFS 2018.2, he no longer receives all notifications emails that are sent either when a pull request is created, or when there is a change on a Work item on the “Assigned To” field. Sometimes users receive emails (but it’s rare) but in most cases emails are not sent.

Before this upgrade, sending emails by TFS worked very well.

Read More

In my previous post I exposed the VSTS task for tag your GitHub source code, that in included in my VSTS extension “GitHub Tools Task” , published in the Visual Studio Marketplace here

For continue to improve this integration of GitHub inside DevOps pipeline in VSTS (Visual Team Services), I included another task in this extension to create a GitHub release with a release notes during your VSTS CI/CD pipeline. You can get more information for create GitHub release manually in the GitHub documentation.

Read More

When using Git source control system, the tag mechanism is one of good practice in great DevOps pipeline.

In VSTS (Visual Studio Team Services) build process, the Tag action option is present by default when the source repository is Git type.

Read More