Hi group, I'm investigating how to include Jenkins CI support in GitVersion <https://github.com/ParticularLabs/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 <https://github.com/ParticularLabs/GitVersion/issues/313>).
GitVersion currently supports TeamCity, MyGet, Continua CI and AppVeyor <https://github.com/ParticularLabs/GitVersion/tree/master/GitVersionCore/BuildServers>. I'd like to add Jenkins to the list. 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 <http://confluence.jetbrains.com/display/TCD65/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-AddingorChangingaBuildParameterfromaBuildStep> . 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6b9e6e79-81f0-4a11-9253-b0c3503c0e9f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
