Azure DevOps Pipelines Hey! You broke our pipeline! One of the advantages of Azure Pipelines is that it automatically updates your tasks to the latest minor version. That way you don't have anything to stay up-to-date. But this also has disadvantages. Both Microsoft and Extension Authors can accidentally break your pipelines.
GitHub Featured Enable RenovateBot for Azure Pipelines In my report on the Security state of the Azure DevOps Marketplace I came to the unfortunate conclusion that about 40% of the extensions contain vulnerabilities. One of the recommendations for both Azure DevOps administrators and pipeline authors was to keep the Azure Pipelines Tasks up-to-date.
Azure DevOps Pipelines Speeding up the Azure DevOps Extension tasks I've been maintaining and using the Azure DevOps Extension tasks for years now and I've always been frustrated by the slowness of some steps.
Azure DevOps Featured Security state of the Azure DevOps Marketplace This report focusses on the Azure Pipelines extensions in the Marketplace. At the time of compiling the report there are 1460 extensions in the "Azure Pipelines" category. More than 500 have one or more vulnerabilities or vulnerable dependencies.
Visual Studio 2022 Adding Visual Studio 2022 to Azure DevOps Server 2020 Visual Studio 2022 is out! But Azure DevOps Server hasn't had a release to support it yet. This means that in Azure Pipelines it won't detect your freshly installed copy of Visual Studio 2022.
Azure DevOps Pipelines Renaming an Azure Pipeline task in an existing Azure DevOps extension I have many Azure DevOps Extensions. Some recent, but also tasks dating back to 2015 when the extensibility model for build tasks forst appeared. Over time much has changed in Azure Pipeline Land...
Azure DevOps Pipelines What to do when your build hangs on the Hosted Pool... When your build freezes and you can't remote into the agent... You're basically blinded...
Azure DevOps Pipelines Solving TFVC error TF14067 and Azure Pipelines When this happens you'll see the following cryptic error message that mentions: A path you are absolutely certain exists; A workspace name that was created minutes before when the build agent initialized; TF14067.
Azure DevOps Azure DevOps Extension Tasks 1.2.3x It's been a while since I last blogged about the Azure DevOps Extension Tasks. Here are the things that have changed since the last update [https://jessehouwing.net/vsts-relnote-ci-cd-tools-for-vsts-extensions-1-1-75/]: * Added support for publishing Visual Studio extensions. * Support for versioning localized Azure Pipeline tasks * Support for executing under Node 10 * Fixed
Azure DevOps Staged execution of tests in Azure DevOps Pipelines When running Unit Tests in your build system, you may want to first run the most important suite, the one that should never fail, the ones that are currently being changed, finally the regression suite that may be slower to execute.
Azure DevOps Pipelines VSTS Build & Release to Azure DevOps Pipelines tasks Out with the old, in with the new! With the rename of Visual Studio Team Services Build and Release Management to Azure DevOps Pipelines all of the underlying libraries are being renamed too. In order to stay up to date and receive the latest updates you'll need to make a
Azure DevOps Tasks and Release Gates on RadioTFS In this episode of RadioTFS we spoke about the Global DevOps Bootcamp, Azure Pipelines and more specifically Release Gates and setting up a pipeline for your own Azure DevOps Extensions and some other recent blog posts.
Azure DevOps Pipeline extension scoped to a specific TFS or Agent version In The Netherlands more and more cities are creating an artificial wall around the city centers for older cars, certain fuel types or lorries. This is happening elsewhere in Europe as well. A similar things needs to happen in the Azure DevOps marketplace now that the number of supported target
Azure DevOps Fail your builds when tests are skipped in Azure DevOps Pipelines When the Visual Studio Test Task in Azure DevOps Pipelines fails to find any tests it logs a warning and happily succeeds. It has been a regular request on the MVP community to do something about that and to ensure that builds fail when no tests have executed. Since test
Azure DevOps Azure DevOps Extension Tasks 1.1.75 I'm happy to announce that version 1.1.75 of the Azure DevOps Extension Tasks is rolling out to the Visual Studio Marketplace. The last few releases have added a couple of significant features that I'd like to quickly highlight in this post.
Quality Code Featured Hard lessons in asynchronous JavaScript code Last Friday I received a bug report for one of the extension I maintain. It took a while to first reproduce the case and then to figure out what was happening exactly. I found that my assumption about the execution order didn't match reality and that I was fighting a race condition.
Ghost Continuous Delivery of customized Ghost themes using VSTS In order to migrate my Ghost blog I needed to customize the default theme to support some of the features I'm relying on: - Disqus comments - Google Analytics - Integrating Google+ comments. To be able to quickly integrate updates I'm maintaining a fork of the Casper theme with my changes.
Azure DevOps Featured Crafting complex Release Gate conditions in VSTS A recent addition to VSTS is the ability to run a quick check prior to triggering a release to an environment. These checks can be used to check that there are no new customer complaints, no important jobs running in the environment etc. This post explains how to build your own.
Azure DevOps New versions of TFS/VSTS build tasks I just pushed out new versions of the following tasks: * MsBuild Helper Task [https://marketplace.visualstudio.com/items?itemName=jessehouwing.jessehouwing-vsts-msbuild-helper-task] * Fixed a number of bugs when the Agent's work folder has a space in it somewhere. * Snyk [https://marketplace.visualstudio.com/items?itemName=jessehouwing.vsts-snyk] * Fixed auto-update of built-in
Azure DevOps Pipelines Extending your Build and Release pipeline The new build and release engine that ships with Visual Studio Team Services and Team Foundation Server 2015 (The Release Management bits shipped with TFS 2015 update 2) provides a whole new way of configuring your Continuous Integration and Deployment pipeline. A much improved and simplified way. You may have
Azure DevOps Automatically populate your Source branch when publishing to Sonar When you enable your build definition to trigger on multiple branches, you may not want them all to publish into the same Sonar project. Sonar has the concept of Branches, they're simply appended to the Project Key with a -. This prevents an old Hotfix build from messing up the
Azure DevOps Define a custom Authentication Scheme for your VSTS extension The standard Authentication Schemed in VSTS include Basic (username/password), Token, Service Credential (for Azure) and AzureCertificate Authentication. If you simply need a username password or a Personal Access token you can derive your own Credential Type from one of the exiting Authentication Schemes. You can see an example of
Azure DevOps Access all available build variables from your VSTS Build task > This StackOverflow answer covers the options in the Node and PowerShell3 handlers [https://stackoverflow.com/a/55610724/736079]. NOTE: This cmdlet works with the Powershell host that shipped with TFS 2015 RTM and which will be replaced with a new task runner. Whether this functionality will remain, is uncertain [https:
Azure DevOps Binary promotion of Visual Studio Team Service Extension When creating a Visual Studio Team Services extension (such as a collection of build tasks), it makes sense to publish it as a privateextension first. You can do this by overwriting the extensionid from the commandline, but there is no direct commandline switch to override the visibility of an extension.
TFS 2015 Publish Build Tasks to TFS 2015 without configuring Basic Auth on the server When you want to publish build tasks to a TFS 2015 server, you need a Basic Authentication enabled endpoint. Unless your server is configured with SSL, this is a major security concern. Until now the guidance I received was to setup a second Application Tier, configure it with Basic Auth
