To setup a VSTS (Visual Studio Team Services) account initially is very easy. The default user directory that is behind VSTS is a directory based on Microsoft Accounts (MSA). Quite some companies start by using MSA’s to access their VSTS instance and then decide to make the move to Azure Active Directory (AAD) once relevant data is already stored, but then face some issues.
At a customer I’m implementing automated deployment for one of their web applications. We’re using a PowerShell DSC script that is kicked off by Release Management (which is part of Microsoft Team Foundation Server). Part of that script is a “File” resource which takes care of actually deploying the new files. Continue reading
Today I updated our SonarQube instance from version 5.2 to version 5.3. After reading through the release notes and the upgrade documentation and with the previous upgrade fresh in my mind I started by making an additional backup of the database.
You might have already come across this acronym; ARA (Application Release Automation). As part of DevOps practices, this is not only the process of automating the actual installation of an application (landscape), but also involves moving the application through the deployment pipeline (e.g. dev > test > acc > prod).
Find all of my tweets published during the keynote sessions of Microsoft Connect(); event on November 18th, 2015.
Today I was adding another (generic) Service Endpoint to Visual Studio Online in order to integrate one of our Team Projects with SonarQube. This Service Endpoint is the link that describes how the Build should connect to SonarQube. While creating it I got an error “User does not have required permissions for the service endpoint”