Visualize the health of your CI/CD pipelines

The latest Team Project Health v1.2 extension, created by Wouter de Kort, Jakob Ehn, Utkarsh Shigihalli, and Ed Elliott, enables users to visualise the overall health of builds and releases. When you’re running multiple CI/CD pipelines, it’s important to visualize their overall health. This DevLabs extension contains a number of dashboard widgets, that enable users…

3

Help us refine our extensibility focus and energy from gap filling to enablement

To ensure that we deliver value, we’re continuously adapting our focus and strategy. We’re reviewing our extensibility strategy for the coming few months and need your feedback to be successful. Are delivering value to you? Are we missing important adoption blockers, feature gaps, or ideas?  Please take few minutes to read this post and share…

0

What is in the latest releases of the team services extension generator?

We’re pleased to announce another update for the yeoman generator-team-services-extension, delivering new features, template improvements, and improvements to your CI/CD pipelines. Team Here’s a quick snapshot of the team that implemented the innovations covered herein:  Mikael Krief (lead) … Hosam Kamel    Tiago Pascoal Updates Remember to bookmark aka.ms/vsarreleases, which summaries all of the feature…

0

How to integrate Application Insights monitoring in your Team Services extension

Monitoring your team services extension is an important DevOps practice. In this article we’ll demonstrate how to integrate Application Insights telemetry in your extension by using our new Telemetry Client for Team Services extension. Prerequisite – You need an Azure subscription and an Application Insights resource. Step 1: Required modules Reference two npm modules dependencies…

2

How to create or upgrade your team services extension in 4 steps

My contribution to the Yeoman generator for the VSTS extension project helped me improve the way we create extensions. Starting from the way we structure the extension files, the JavaScript minification, how we generate and publish the extension package and down to monitoring the extension usage. The goal of this post is to walk you…

0

Debug Yeoman team-services-extension in 5 steps

I recently ran into a bug while trying team-services-extension yeoman generator on macOS. The bug doesn’t affect the overall generator flow it just causes the generator to fail in the last step when packaging the extension into vsix. The bug is now fixed in the latest release v1.0.35, Visual Studio Code was my best buddy…

0

Setup a CI/CD pipeline with package management for your Team Services extension

In recent posts we covered our CI/CD pipelines for the Yeoman generator package, for simple extensions, and for extension with unit testing and code coverage. We continue by exploring our Roll-up Board extension pipeline, which pulls a shared package from the Package Management in Team Services. These CI/CD pipeline posts are based on our Applying…

0

Where can I find the Visual Studio ALM Ranger bits? Bookmark one URL!

If you are reading this post you’re already in the right place! We’re often asked by users where they can find our latest artefacts, for example guidance, tools, testimonials, videos, articles, and research findings. Well, it’s evolving on CodePlex, GitHub, Channel9, Marketplace, and many other interesting places. Finding our bits Remember the aka.ms/vsar URL, where…

0

Breakpoint Generator extension is open source

As requested by the community, we open sourced the Breakpoint Generator after an update to support Visual Studio 2017. See Breakpoint Generator Extension Announcement and the for an overview of the extension. Get the latest bits   Thank you to the team! Contributors – Jakob Ehn, Utkarsh Shigihalli Product owners – Andrew Hall, Andy Sterland…

0

Set up a CI/CD pipeline with unit testing and code coverage for your Team Services extension

We receive a notification that there’s a pull request to review for our Team Services extensibility project. We discuss the proposed changes as a team, eventually merge the new feature(s) into the master branch, and close the pull request. Done … right? Not quite. The merge triggers our automated CI/CD pipeline, which consistently builds, tests…

0