You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2020. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
I'm sorry but I haven't had any time to look at the open issues. As you can understand this is an open source project that I do in my free time. I hope I can find some more time in the future but for now the project is on hold.
Sorry,
Wouter
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: