alm-rangers / visualize-team-project-health-widgets Goto Github PK

Is there a way to configure each widget to poll or add a webhook to a build/release pipeline? For example polling the status every 60 seconds would be great.

The default refresh time for dashboard is 5 minutes and it's too long for our builds. Also it makes the build monitor too flickery while it's in the middle of the office.

Dashboard card: Release Health Detail; is empty when the release was abandoned (third tile)

We're using a less file for the CSS styling of the widgets. For now, I've installed a VS Code extension that creates the .css file at save and I've added app.css to source control. It would be nicer if webpack would do the compilation and minification of the less file at build.

We use a large nuber of builds, over 300. We use folders to group them and it would be great to select a folder and have all builds automatically included, same for releases.

Thank you

We have a multi-stage (environment) release pipeline. It would be great to be able to pick the specific stage against the release health widget. As far as I can see it only allows for a release definition to be picked so it is not possible to target the results to a given stage.

Wondering if this repo is supposed to hold the extension https://marketplace.visualstudio.com/items?itemName=ms-devlabs.TeamProjectHealth

Hi,

On promise 2017 CU3, version 1.2.62

When I add any of the build/release widgets get erreur
'Promise' is undefined

Any help would be appreciated

The Release Health Detail widget stays in the state of in progress (blue with round arrow) for a release which contains tasks that execute tests that do not all pass. Removing the test tasks allows the widget to display a success state (green with check). The desired behavior is that the widget would turn either yellow or red to match the state of the release.

This particular release is setup with a single stage that has two jobs. The first job deploys the code (RESTful API) to the environment and the second job uses Newman(PostMan) to execute a series of requests to the RESTful API.

Here is an image of the release tasks:

Hi,
Few of widgets stopped to work:

On premise TFS 2017 (Version 16.131.28226.3)

Regards
-Roman

Even though #5 has been fixed about 2 years ago, it doesn't seem to be released yet. Would it be possible to provide an up to date release?

The config dropdown for the Build Health Details only shows three of my builds. Older ones. It looks like it is only grabbing builds from the first folder in my Build Definitions, but I don't know where to configure this.
Where does that list of build definitions come from, and is there a way to configure it?

POST https://dc.services.visualstudio.com/v2/track receiving
400 (Invalid instrumentation key)

Currently Release widgets display the same icon whether the Release is In Progress or is Waiting Approval.
It would be nice if these 2 status may be differantiated.
Some kind of clock icon may represent Waiting Approval status.

I want to track any changes that made by my team, will this extension work?
include any new comment.

Replying to #12 ,
The missing content types are for html files. They are always missing when I download MS extensions from the marketplace, or github. I deploy them to an on-prem TFS (2017U3) using Tfx-Cli, and if I don't add "contentType": "text/html" entries to the files object in vss-extension.json for all served .html files, all my browsers just download, or offer to download, html files instead of displaying them. I'm guessing later versions of TFS/ADO correctly infer the contentType from the file itself, and you don't deploy to the versions that don't (like 2017U3). Either that, or your deployment is adding the missing content types, at some point, to the manifest (but not committing those changes). Or I guess it's possible our app tier's web server is not configured properly.

I am using 'Build Health Overview' widget that is configured on a specific build pipeline in azure DevOps and that build pipeline have N number of succeeded builds and M number of failed builds.
But, 'Build Health Overview' showing 1 succeeded, 0 failed, 0 running builds instead of N succeeded, M failed, 0 running builds.

The same issue with 'Release Health Overview' widget, it is configured on a release pipeline that has some stages and total 5 past releases but in the dash-board, it is showing 0 succeeded, 2 failed, 0 running releases.

Attaching the screenshot of dashboard and release pipeline for 'Release Health Overview'

Regards,
Vikash

When monitoring I only want to see builds that are triggered on the master branch (or any specified branch), even if the same build can be used for multiple branches.

I can't find information to verify the overview is for all builds in the project ever.

If so (as I suspect), is there a way to filter? (ie last 30 days) or to see the count over time?

very confusing.. there must be a filter of some kind running here.

I have these wonderful widgets installed for our TFS 2018 onprem. When I open build info by clicking on Build health details widget from the dashboard I have an error:

Does this extension fully support TFS 2018 onprem?

This doesn't work in IE11. It says "widget cannot load" and then "Promise is undefined". It can be fixed by installing es6-promise and adding import "es6-promise/auto"; to the top of various .ts files. Sorry I can't submit a PR; I'm waiting for my organization to finish some paper work that would allow me to do that without getting fired.

Also, there are missing html content types in your vss-extension.json which prevents the page from displaying in any browser (in on-prem TFS2017U3, anyway) if anyone tries to rebuild/redeploy from your source. This seems to be true for all (or almost all?) extensions created by Microsoft or by ms-devops or by ALM Rangers.

Not supporting Microsoft Internet Explorer is also a seemingly universal shortcoming of Microsoft web extensions.

Hi 👋

Is this project still active? It appears that a few fixes have been merged but hasn't been released.

If there isn't a response from owners, would the community be interested in contributing to a fork?

Build definitions with similar names are included in results.

Steps to reproduce

1. Create builds with similar names: Foo.Bar and Foo.Bar.Gated

2. Configure Build Health Overview only for build Foo.Bar.Gated

3. Run both builds

Result

The overview shows results from both build definitions.

Investigation
This line is the culprit:
definitions = definitions.filter(def => customSettings.selectedDefinitions.indexOf(def.name) != -1);

Foo.Bar is present within string Foo.Bar.Build
Thus not filtered from the original set of build definitions

proposed solutions

1. split customSettings.selectedDefinitions and check for full match
2. when selecting builds store the build id's in customSettings.selectedDefinitions (note: when a build is regenerated and gets a new id it won't be in the results)

The list of Build defintions for "Build Health Overview doesn't render very well so difficult to use. Screenshot below