-
Notifications
You must be signed in to change notification settings - Fork 27
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
Comments
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! |
Excellent, looking forward to it! Great-looking screen, BTW. |
Excellent tool guys! I just installed it to test it out. |
+1 for this. Love the visual approach taken here - but like the previous commenter, just moved everything over to vNext :( |
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 :) |
Thnx guys! Downloading it now to test it out. |
I have compiled and placed the new version, but my VNext builds are not showing. |
@rpong79 did you change your config file? See the changes here: |
Hi @on5sl . |
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 ? |
There is no info in the log that is usable. A collegue checked and could it
|
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. |
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
|
Hi |
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. 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. |
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.. |
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! |
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. |
Buildscreen seems to show old-style XAML builds, and not the new vNext builds. Is that expected?
The text was updated successfully, but these errors were encountered: