Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 15 2020 13:06
    arturcic unlabeled #2095
  • Jun 15 2020 13:05
    arturcic opened #2328
  • Jun 15 2020 08:09
    github-actions[bot] commented #2122
  • Jun 15 2020 08:09
    github-actions[bot] commented #2300
  • Jun 15 2020 08:09
    github-actions[bot] commented #2306
  • Jun 15 2020 08:09
    github-actions[bot] commented #2310
  • Jun 15 2020 08:09
    github-actions[bot] commented #2311
  • Jun 15 2020 08:09
    github-actions[bot] commented #2320
  • Jun 15 2020 08:09
    github-actions[bot] commented #2327
  • Jun 15 2020 07:49
    arturcic milestoned #2095
  • Jun 15 2020 07:49
    arturcic demilestoned #2095
  • Jun 15 2020 07:46

    arturcic on 5.3.6

    (compare)

  • Jun 15 2020 07:27
    arturcic demilestoned #2241
  • Jun 15 2020 07:27
    arturcic unassigned #2241
  • Jun 15 2020 07:27
    arturcic demilestoned #2074
  • Jun 15 2020 07:26
    arturcic milestoned #2327
  • Jun 15 2020 07:25
    arturcic demilestoned #2318
  • Jun 15 2020 07:25
    arturcic milestoned #2122
  • Jun 15 2020 07:25
    arturcic labeled #2122
  • Jun 15 2020 07:23
    arturcic demilestoned #2313
Tomasz Cielecki
@Cheesebaron
This a internal build machine on our local network
Gary Ewan Park
@gep13
Ah, ok, so that makes more sense.
Tomasz Cielecki
@Cheesebaron
Seems like, even though clean is enabled in Azure Pipelines it leaves local branches floating around
Seems like, even though clean is enabled in Azure Pipelines it leaves local branches floating around
My own internal one
Asbjørn Ulsberg
@asbjornu
@aeos, your use-case sounds rather special and not something GitVersion is rigged for out of the box, but if develop works as you expect, you can just give feature branches mode: ContinuousDeployment as well.
henrik eriksson
@henrik_GJ_Esson_twitter
@Cheesebaron have you verified that this is not a several step cache being used? E.g. if there is one cache being used for all the builds, which are copied to local build folders for the explicit builds. Both the cache and the build folder needs to be verified to be clean...
henrik eriksson
@henrik_GJ_Esson_twitter
According https://gitversion.readthedocs.io/en/latest/more-info/version-increments/, gitVersion calculates the next semver version. But when I tested setting version 1.2.3 in the branch name, gitversion tells me the assemblySemVer version is 1.2.3
Should it be like that?
henrik eriksson
@henrik_GJ_Esson_twitter
When working with GitVersion in CI environment, must full repo be used? Or shallow clones possible(seems so to me). And on single branches(possible? not recommended?)
...related to speeding up the build environment
henrik eriksson
@henrik_GJ_Esson_twitter
Noticing that shallow clones is fine. But gitversion requires a master or development branch to be present. So CI builds on single branch does not work
Asbjørn Ulsberg
@asbjornu
I suppose it depends on how shallow the clone is. GitVersion needs enough history to find a version source, which will often be a tag. If no source can be found in the history, it will crash.
Igor Artamonov
@splix
I wanted to try GitVersion tool in our project, to tag builds during CI. We use CircleCI and Travis, and none of them comes with GitVersion preinstalled. I was trying to find a release for non-windows os, but don't see any. 'apt-get install gitversion' can't find it too. Am I missing something, or how people use it with circleci/travis?
Kim J. Nordmo
@AdmiringWorm
most projects I've seen make use of the GitVersion.Commandline nuget package (which requires mono on non-windows systems).
There is also a .NET Core global tool called GitVersion.Tool that can also be used (no stable release of this one yet though)
@splix ^^
Igor Artamonov
@splix
Can you please to point to any of such project? open soruce I mean. want to take a look at their CI configs
because I have no idea what is nuget package actually :) and how to install it
ah, maybe I’ve found a project with such travis config. trying now
Kim J. Nordmo
@AdmiringWorm
I see. The projects I've seen using it, mostly build on Windows (some do on Linux as well), and all of them makes use of something called Cake to orchestrate the build, which then pulls down the nuget packages the owners want to use.
This may not apply to you though unfortunately
not seen anyone using the cmd directly yet though.

ah, maybe I’ve found a project with such travis config. trying now

Good luck

Igor Artamonov
@splix
I've found a .travis file on github with following line dotnet tool install -g GitVersion.Tool --version '4.0.1-*’, I guess it does what I want. Though I don’t see any calls of GitVersion in that repo, that’s strange
Kim J. Nordmo
@AdmiringWorm
They probably makes use of dotnet gitversion or dotnet-gitversion somewhere in the repo. Most likely in a build script (would at least be my guess)
Igor Artamonov
@splix
Ah, you’re right! they do dotnet gitversion I’ve missed that line. Thank you!
Kim J. Nordmo
@AdmiringWorm
:+1:
Igor Artamonov
@splix
it seems that dotnet command works only if you build csharp project :(
Kim J. Nordmo
@AdmiringWorm
oh right, I completely forgot about that. You probably would need to use the mono edition of gitversion then.
Did some digging around, and found something that may be of some use to you: https://sedders123.me/2017/07/28/install-gitversion-on-ubuntu/
I haven't tested that article though, as I'm not using ubuntu (which I believe travis uses)
Igor Artamonov
@splix
Thank you!
Kim J. Nordmo
@AdmiringWorm
no problem, hope that helps you at least a little
Calvin Dallmore
@aeos
@splix not that this is what you want, but if you use dotnet cake with GitVersion.Tools then you can use GitVersion in a build setup and use the versioning for other project types.
henrik eriksson
@henrik_GJ_Esson_twitter
I'm using the default settings in gitVersion, and the approach to determine the next version based on the commit message.
One thing is strange: '+semver: Patch' and '+semver: Skip' ends up in the same result
that patch number is increased
It should not be increased on skip, right?
henrik eriksson
@henrik_GJ_Esson_twitter
is there a smoother way to get gitVersion to calculcate the new version. instead of tampering with the commit message?
Gary Ewan Park
@gep13
@henrik_GJ_Esson_twitter I use gitflow, and I have never needed to tamper with commit messages to bump version number.
You have an option to specify the "next" version number in the configuraiton yml file
henrik eriksson
@henrik_GJ_Esson_twitter
THen the next version is automatically defined based on what type of branch you merge?
Gary Ewan Park
@gep13
If you follow the processes outlined by GitFlow, then GitVersion respects that, and asserts the correct values, derived from branch names, yes
henrik eriksson
@henrik_GJ_Esson_twitter
Well...we do not fully follow gitFlow. I would say it's gitFlow "style"
But manual selection of the version is the target
Hence the tampering with the commit message
Gary Ewan Park
@gep13
Based on what you have said, I think the best way forward might be to specify what the next version is going to be in the yml file, and from there, GitVersion will use that as the base version, to derive the exact version number from.
henrik eriksson
@henrik_GJ_Esson_twitter
Next version e.g. 5.5.5 and then it will calculate based on what is merged?
if feature branch is merged, then it will increase minor. bugfix will increase patch
Gary Ewan Park
@gep13
A feature branch merge, according to gitflow wouldn't change major, minor or patch version number. Only moving to a release branch or hotfix branch would change the semantic version number. GitVersion follows these basic rules.
henrik eriksson
@henrik_GJ_Esson_twitter
Looking at our installer(advancedInstaller) it does not support semantic versioning for non public releases. Which causes some confusion for internal management of versioning for development versions.
henrik eriksson
@henrik_GJ_Esson_twitter
I realised I missed out on a sentence in semantic versioning, that patch set increases even though there is no change in the public api