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

Support for vNext builds: Issue with TFS 2015 On-Prem #7

Open
tscott98 opened this issue Dec 2, 2015 · 18 comments
Open

Support for vNext builds: Issue with TFS 2015 On-Prem #7

tscott98 opened this issue Dec 2, 2015 · 18 comments
Assignees

Comments

@tscott98
Copy link

tscott98 commented Dec 2, 2015

Buildscreen seems to show old-style XAML builds, and not the new vNext builds. Is that expected?

@mdb1988
Copy link
Member

mdb1988 commented Dec 2, 2015

Hi Tim,

Yes, xaml builds are currently the only supported ones. We were already discussing adding support for the new build definitions though, so stay tuned!

@tscott98
Copy link
Author

tscott98 commented Dec 2, 2015

Excellent, looking forward to it!

Great-looking screen, BTW.

@robinong79
Copy link

Excellent tool guys! I just installed it to test it out.
We have migrated all our builds to vNext so we can't use it at the moment, but I will keep an eye out on this feature.

@tomorgan
Copy link

+1 for this. Love the visual approach taken here - but like the previous commenter, just moved everything over to vNext :(

@on5sl
Copy link
Contributor

on5sl commented Dec 24, 2015

After some testing and fixing vNext builds are now supported! Will you guys compile the binaries yourself or do you want us to make them available somewhere? Thanks to @robi26 for making this possible :)

@robinong79
Copy link

Thnx guys! Downloading it now to test it out.
Thumbs up!

@robinong79
Copy link

I have compiled and placed the new version, but my VNext builds are not showing.
Is there a setting in the config that I need to adjust?

@on5sl
Copy link
Contributor

on5sl commented Dec 24, 2015

@rpong79 did you change your config file? See the changes here:
robi26@76af716#diff-bb34a5a1257a06e6cc39f003f3c479a7

@on5sl on5sl self-assigned this Dec 24, 2015
@robinong79
Copy link

Hi @on5sl .
I have deleted my old files and placed the new build. After checking I have the latest web.config.
Some extra info: I am trying it on TFS 2015 on premise. He will load the XAML definitions though.

@on5sl
Copy link
Contributor

on5sl commented Dec 24, 2015

We didn't test it yet on TFS2015 on premise i'm afraid. I'm not able in doing so either. Do you have some valuable information in OrbitOne.BuildScreen/Log/Log.txt ?

@robinong79
Copy link

There is no info in the log that is usable. A collegue checked and could it
be that the microsoft assemblies need updating? Happy Christmas 😁
Op do 24 dec. 2015 om 15:01 schreef Bram Verswalm [email protected]

We didn't test it yet on TFS2015 on premise i'm afraid. I'm not able in
doing so either. Do you have some valuable information in
OrbitOne.BuildScreen/Log/Log.txt ?


Reply to this email directly or view it on GitHub
#7 (comment).

@on5sl
Copy link
Contributor

on5sl commented Dec 24, 2015

this could very well be the case. Unfortunately i have no environment where i can test for TFS 2015! And my time is up for today. If you can provide me a an account on your TFS for testing purposes i can try to see what the exact problem is.

@robinong79
Copy link

My time is also up. I will debug some more on monday. Can't provide an account I'm afraid.

Will keep you posted. Merry Christmas.

Verstuurd vanaf mijn iPhone

Op 24 dec. 2015 om 16:00 heeft Bram Verswalm [email protected] het volgende geschreven:

this could very well be the case. Unfortunately i have no environment where i can test for TFS 2015! And my time is up for today. If you can provide me a an account on your TFS for testing purposes i can try to see what the exact problem is.


Reply to this email directly or view it on GitHub.

@robi26
Copy link
Contributor

robi26 commented Dec 26, 2015

Hi
Sorry, can't test it on-prem TFS 2015 neither. May well be, that you'll have to update your TFS as MS ins constantly updating VSTS....

@tscott98
Copy link
Author

tscott98 commented Jan 5, 2016

I've fetched the latest version (as of yesterday), and vNext builds do not show up for on-prem TFS 2015 for me, either.

It seems that IBuildServer does not return vNext builds, at least for on-prem TFS. The suggested solution seems to be to use the newer BuildHttpClient, instead.

https://social.msdn.microsoft.com/Forums/vstudio/en-US/80b3beab-9c27-4aeb-88b6-3c84c26e4530/query-vnext-builds-using-ibuildserver?forum=vsx

I've written a command-line build status tool using this client, and it does indeed return the vNext builds from our on-prem TFS 2015 installation.

@on5sl on5sl reopened this Jan 5, 2016
@on5sl on5sl changed the title Support for vNext builds Support for vNext builds: Issue with TFS 2015 On-Prem Jan 5, 2016
@ghost
Copy link

ghost commented Apr 15, 2016

Hey guys, we really like the TFS Buildscreen tool! But just like many others, we're switching to vNext build configurations and they do not seem to show up for TFS on prem. Any news on this issue? We've tried forking a brach and using the new BuildHttpClient, but unfortunately, without success..

@on5sl
Copy link
Contributor

on5sl commented Apr 15, 2016

Unfortunately we didn't had time yet to set up an on prem TFS 2015 server for testing purposes. This is a side project we are running with the team, so i can't guarantee a certain date...I'll keep you guys posted once we start working on it!

@ivoloshin
Copy link

ivoloshin commented Apr 15, 2016

Having switched to vNEXT builds, I did an extensive search for a dashboard that supports it. I only found Team Build Screen to support it: https://teambuildscreen.codeplex.com/ It's only in their development branch, so you'd have to check it out and build the binary yourself, but it seems to work and that's what we're using.

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

7 participants