Hi group,
I'm investigating how to include Jenkins CI support in
GitVersion, a command line utility for .NET that uses conventions to derive a SemVer product version from a GitFlow or GithubFlow based repository (issue
#313).
Current implementations work by writing out specific messages to the build output, which are picked up by the build server. In TeamCity, this concept is called "Service Messages". Service Messages can be used to add and/or set build parameters, as described
here in the TeamCity documentation.
I did some investigation, but I did not find a similar mechanism in Jenkins. A similar question was raised
here on this newsgroup about a year ago, but received no answers.
If Jenkins supports a concept similar to TeamCity's service messages, could you point me to its documentation?
Or should I use a completely different mechanism to add/set build parameters from within an executing job?
Thanks group,
~Marijn