Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Results Service #18

Open
kdelorey opened this issue Apr 18, 2019 · 4 comments
Open

Build Results Service #18

kdelorey opened this issue Apr 18, 2019 · 4 comments

Comments

@kdelorey
Copy link

In an attempt to add a new tab to the build results page using the ms.vss-build-web.build-results-view target and ms.vss-build-web.build-results-tab type I found that there doesn't seem to be a way to retrieve contextual information about a build that a user is viewing.

There is a IBuidPageData service, but it does not work on the build results view. If I try an manually try and grab the build ID (to use with the REST client) out of the parent window's URL I'll get a cross-site origin error.

Can something be added to retrieve build result information?

Related: build-results-enhancer

@NickHeap2
Copy link

I'm having this same issue. @kdelorey did you manage to find any work arounds?

@kdelorey
Copy link
Author

@NickHeap2 I did not unfortunately, and I had to move on to other things. I'll be very interested to know if you find anything out.

@rouke-broersma
Copy link

If anyone is looking for a workaround (this still has not been fixed), I used this ugly hack that works for some reason:

const config = SDK.getConfiguration();

// ugly, onBuildChanged has magic callback to return BuildReference, this is not documented anywhere
config.onBuildChanged(async (build: BuildReference) => {
    console.trace("Current build is {0}", build);
}

@xakep139
Copy link

If somebody still needs a solution for this issue, please try this: microsoft/vsts-extension-samples#143 (comment)

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

No branches or pull requests

4 participants