Skip to content

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

Open

Description

@tscott98

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

Activity

  1. mdb1988 commented on Dec 2, 2015

    @mdb1988
    Contributor

    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!

  2. tscott98 commented on Dec 2, 2015

    @tscott98
    Author

    Excellent, looking forward to it!

    Great-looking screen, BTW.

  3. robinong79 commented on Dec 4, 2015

    @robinong79

    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.

  4. tomorgan commented on Dec 22, 2015

    @tomorgan

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

  5. on5sl commented on Dec 24, 2015

    @on5sl
    Contributor

    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 :)

  6. robinong79 commented on Dec 24, 2015

    @robinong79

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

  7. robinong79 commented on Dec 24, 2015

    @robinong79

    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?

  8. on5sl commented on Dec 24, 2015

    @on5sl
    Contributor
  9. self-assigned this
    on Dec 24, 2015
  10. robinong79 commented on Dec 24, 2015

    @robinong79

    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.

  11. on5sl commented on Dec 24, 2015

    @on5sl
    Contributor

    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 ?

  12. robinong79 commented on Dec 24, 2015

    @robinong79

    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 notifications@github.com

    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).

  13. on5sl commented on Dec 24, 2015

    @on5sl
    Contributor

    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.

  14. robinong79 commented on Dec 24, 2015

    @robinong79

    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 notifications@github.com 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.

  15. robi26 commented on Dec 26, 2015

    @robi26
    Contributor

    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....

  16. tscott98 commented on Jan 5, 2016

    @tscott98
    Author

    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.

  17. reopened this on Jan 5, 2016
  18. changed the title [-]Support for vNext builds[/-] [+]Support for vNext builds: Issue with TFS 2015 On-Prem[/+] on Jan 5, 2016
  19. on5sl commented on Apr 15, 2016

    @on5sl
    Contributor

    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!

  20. ivoloshin commented on Apr 15, 2016

    @ivoloshin

    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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions