Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Build status icon should allow multiple build definitions #146

Closed
letmaik opened this issue Mar 9, 2017 · 2 comments
Closed

Build status icon should allow multiple build definitions #146

letmaik opened this issue Mar 9, 2017 · 2 comments

Comments

@letmaik
Copy link
Member

letmaik commented Mar 9, 2017

If a git branch triggered several builds (e.g. Linux and Windows), then currently clicking on the build status icon open a random build. Given that there is no overview page in VSTS for all builds related to a push, the build icon should have a selector for navigating to a specific build, which would also display the build status individually if one of two builds failed for example.

@jeffyoung
Copy link
Contributor

Hi @letmaik. Right now, the items that you can add to the VS Code status bar allow you to do just a few things like set the octicon, add a tooltip and provide a command. Ideally, you could add additional UI so that, on click, you could show a list of items in a 'fly out' menu (like multiple builds). Today, that's just not possible.

If I understand well, you've got multiple CI builds that kick off when a push occurs on a certain branch. The API we use today asks the server to give us the state of the build related to a particular branch and repository. It's likely that the 'randomness' is related to which build completes first and at what time the build status is requested by the extension.

We can spend some time thinking of other solutions to the issue (perhaps allowing multiple builds to be tracked).

Thanks for the feedback and trying out the extension!

@Jaykul
Copy link

Jaykul commented Jul 27, 2017

How about (as a minimum) making the "team.buildDefinitionId": 0, setting work even with tfvc -- at least then we could force the one we care about the most?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants