When running GitVersion on buildserver /output json is ignored

[Philo]

When running GitVersion on a build server (tested with teamcity), the:

/output json

parameter is ignored in favour of

/output buildserver

If an output type is explicitly specified it should be honoured?

[JakeGinnivan]

It can only be one or the other. /output buildserver writes lots of stuff to stdout, which makes it impossible to output a json value.

The pull requests relating to the command line changes talk about this.

[Philo]

I'm not looking to be able to have mulitple output types, but if for example I am running a build on appveyor, but have a custom build process (via gulp) and I am calling gitversion from a gulp task I want gitversion to return the json output via

/output json

However when appveyor is detected the json flag is ignored so my gulp task never receives the expected json output from stdout.

[gep13]

@Philo how exactly are you triggering GitVersion on AppVeyor?

AppVeyor immediately makes the asserted version number available via Environment Variables as you can see here:

https://github.com/chocolatey/ChocolateyGUI/blob/develop/BuildScripts/default.ps1#L440

In my build for ChocolateyGUI. I call GitVersion using /output buildserver and then consume the environment variable for later processing.

Would that work for you?

[pascalberger]

Calling /output buildserver and consuming the environment variables might be best practice in most cases, but shouldn't it still be possible to call GitVersion.exe /output json from a gulp task and get the json output to stdout? I don't see why this shouldn't be possible and assume this is a bug, since on buildserver we explicitely call /output buildserver which would be useless otherwise.

[gep13]

@pascalberger oh yeah, I don't disagree on that score. The request for a json output should definitely be respected.

[Choc13]

Is there any chance of this issue getting fixed? I'd also like to use /output json on a build server from within a gulp task.

[JakeGinnivan]

This seems to work for me. if I set a environmental variable which triggers the normal service messages then instead do /output json then I get the json string.

Can someone let me know how to reproduce

[JakeGinnivan]

Going to close this, I can only assume it got fixed

The only caviet which may be the source of the issue. If you pass /project or /exec to gitversion it will always use /output buildserver. Not sure why that is, but that logic exists. But there is nothing in there that I can see which would cause the issue. Also a fresh clone of a repo and $env:APPVEYOR=1 to trigger build server mode still outputs json.

[JakeGinnivan]

Just a follow up, adding a test in to make sure that it is actually fixed. Which it is :)