Use convention to derive a SemVer product version from a GitFlow based repository
So I started making a GitHub Action that would install GitVersion so I could then use it in further GitHub Actions
I was encouraged by the 5.1.1 release: https://github.com/GitTools/GitVersion/releases/tag/5.1.1
because it was the first to have artifacts for each OS
I then realized that GitVersion is included by default with Windows based GitHub Actions
I still wanted what I wanted when I wanted it, so I created a GitHub Action for mac and linux that would install GitVersion 5.1.1
It was really just me wanting to know how to make a GitHub Action at that point
all that said, I'm going to open the proper pull requests, to get GitVersion v5.1.1 included by default for linux and mac GitHub Actions
this is what makes it available to windows GitHub Actions
this is the issue i opened to get it added to mac/linux
and the PR
@StanleyGoldman have you considered to install the gitversion global tool instead? As .net ask is already installed on those images and can run the tool. Basically you could have something similar to https://marketplace.visualstudio.com/items?itemName=gittools.usegitversion
.net SDK
There are so many ways to use GitVersion, which is definitely great
i just always felt partial to using it on the command line
lol :smile:
in the latest version of GitHub Actions, the new script-able CI system from GitHub
allows for Windows, Mac and Linux environments
on Windows environments, GitVersion is already installed by way of
choco
on Mac and Linux environments, GitVersion is not
I'm currently migrating a pet project from AppVeyor to GitHub Actions, wanted to use linux, and I did not have
choco by default on linux
I responded by creating a GitHub Action that installs GitVersion in linux and mac: https://github.com/StanleyGoldman/setup-gitversion
After conversing with some coworkers, a maintainer of libgit2 also felt himself in the same corner, and implemented one for himself: https://github.com/ethomson/setup-gitversion
I realize it would be better to get GitVersion's command line tool installed into GitHub Actions for Linux and Mac environments
if nothing else, but for the sake of parity
i hope i've made sense of my verbal thought diarrhea earlier...
Yip, it totally makes sense to get GitVersion installed by default on the base images that ship as part of GitHub Actions. I think there is still some merit in having a GitHub Action that installs the GitVersion .Net Global Tool though. That way, when using another image to run your GitHub Actions, you have the ability to install GitVersion on any OS that has .Net Core installed.
Hi, does anyone have experience with GitVersionTask Nuget by any chance?
if so I have struggled with this for a while: https://stackoverflow.com/questions/58714174/gitversion-nuget-version-to-include-sha
if so I have struggled with this for a while: https://stackoverflow.com/questions/58714174/gitversion-nuget-version-to-include-sha
in short, I'm trying to format my NugetVersion instead of using the default, by adding -{ShortSha} in the end (to versions with prefix)
I am seeing a weird issue with hotfix branches.
GitVersion seems to break with an Object Reference error when I create hotfix/v1.2.1 naming conventions.
Is this normal? Should the name I use for a hotfix branch matter? Seems if I rename the branch at the head after a given commit and push again everything works.
If I am missing something in the docs, I apologize. I am not above reading the manual.
I am currently investigating an issue in my build but was hoping someone could share some pointers: I am getting
Could not load type AsyncCompletedEventArgs from assembly System.Net.WebHeaderCollection (see build log). This occurs when trying to calculate version.
I do not get this exception when running locally:
========================================
AppVeyor-Build_Number
========================================
Executing task: AppVeyor-Build_Number
Executing: "D:/_build/Http-Multipart-Data-Parser/tools/GitVersion.CommandLine.5.1.2/tools/GitVersion.exe" -output buildserver -verbosity Debug
INFO [11/23/19 17:04:23:08] Working directory: D:\_build\Http-Multipart-Data-Parser
INFO [11/23/19 17:04:23:09] IsDynamicGitRepository: False
INFO [11/23/19 17:04:23:11] Returning Project Root from DotGitDirectory: D:\_build\Http-Multipart-Data-Parser\.git\ - D:\_build\Http-Multipart-Data-
Parser\
INFO [11/23/19 17:04:23:11] Running on Windows.
INFO [11/23/19 17:04:23:11] Project root is: D:\_build\Http-Multipart-Data-Parser\
INFO [11/23/19 17:04:23:11] DotGit directory is: D:\_build\Http-Multipart-Data-Parser\.git
INFO [11/23/19 17:04:23:15] Begin: Loading version variables from disk cache
INFO [11/23/19 17:04:23:16] Begin: Deserializing version variables from cache file D:\_build\Http-Multipart-Data-Parser\.git\gitversion_cache\13BE
269124B2E5D159064440AA6A034F4A59A4A0.yml
INFO [11/23/19 17:04:23:21] End: Deserializing version variables from cache file D:\_build\Http-Multipart-Data-Parser\.git\gitversion_cache\13BE26
9124B2E5D159064440AA6A034F4A59A4A0.yml (Took: 58.71ms)
INFO [11/23/19 17:04:23:22] End: Loading version variables from disk cache (Took: 61.41ms)
Finished executing task: AppVeyor-Build_Number