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

What is in the latest releases of the VSTS 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 VSTS 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 VSTS 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

Setup a CI/CD pipeline with package management for your VSTS 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

Set up a CI/CD pipeline with unit testing and code coverage for your VSTS 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

What we delivered in latest releases of the VSTS extension generator

We’re pleased to announce another update for the yeoman team-services-extension, delivering new features, code improvements and performance optimization on generated extensions. Here’s a summary of the latest release v1.0.33 Widget Dashboard Integration You can now generate a dashboard widget. The generated sample contains the widget code and a configuration panel, with some input fields Cleanup…

0

Set up a CI/CD pipeline to run automated tests efficiently

Are you planning to implement automated testing in your pipeline? You probably have a few questions, such as: How does automated testing fit into DevOps? What are some different types of pipeline configurations? What key principles should you keep in mind? This post aims to answer these questions and talk about the automation of tests….

0

Set up a CI/CD pipeline for your VSTS 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 and…

0

Set up a CI/CD pipeline for your Yeoman generator package

We receive a notification that there’s a pull request to review on our Yeoman generator 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 and delivers…

0