Bonobo Git Server VS GitVersion

Bonobo Git Server - git server, I will need this (or similar) but no bug tracking

Look, Bonobo has more than one term, it's not always about the animal. Bonobo is also the name of a git server and a framework for Python

You could host it yourself. I run my own git-server using Bonobo Git Server, but there are lots of other self-hosting options. You can check out the wiki at r/selfhosted to see whats good for you

name: Java Build and Test With Gradle on: [push, pull_request, workflow_dispatch] jobs: build: runs-on: ubuntu-latest permissions: contents: read steps: - name: Checkout uses: actions/[email protected] with: fetch-depth: 0 - name: Set up JDK 23 uses: actions/[email protected] #https://github.com/actions/setup-java with: java-version: '23' distribution: 'oracle' - name: Install GitVersion 6.0.5 for Gradle run: | wget -q -O gitversion.tar.gz https://github.com/GitTools/GitVersion/releases/download/6.0.5/gitversion-linux-x64-6.0.5.tar.gz mkdir gitversion_extracted tar -xzf gitversion.tar.gz -C gitversion_extracted ls -R gitversion_extracted sudo mv gitversion_extracted/gitversion /usr/local/bin/gitversion sudo chmod +x /usr/local/bin/gitversion - name: Setup Gradle 8.11.1 uses: gradle/actions/setup-gradle@v4 #https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#build-with-a-specific-gradle-version with: gradle-version: '8.11.1' - name: Build with Gradle 8.11.1 run: gradle build --scan --warning-mode all dependency-submission: # See: https://github.com/gradle/actions/blob/main/dependency-submission/README.md runs-on: ubuntu-latest permissions: contents: write steps: - name: Checkout uses: actions/[email protected] - name: Set up JDK 23 uses: actions/[email protected] with: java-version: '23' distribution: 'oracle' - name: Setup Gradle 8.11.1 uses: gradle/actions/setup-gradle@v4 with: gradle-version: '8.11.1' - name: Setup Gradle Wrapper run: gradle wrapper - name: Generate and submit dependency graph uses: gradle/actions/dependency-submission@v4

Gitversion: It reads your commit history and generates a semver version out of it. Say you are compiling main branch and have a tag 1.0. Then, you squash 3 PRs. When you build this version, the new version number will be 1.0.3. You can configure it to be smarter about increasing major, minor, patch fields. I typically use prefix on the commit messages so that it generates versions correctly. See more at https://gitversion.net/docs/

GitVersion is not available by default and needs to be installed beforehand if we want to use the features it offers. The action is available here.

Check this out https://gitversion.net/docs/

At work we use https://gitversion.net/docs/ in our devops pipelines. Similaf to git-semver it generates a version based on what's published previously.

Under Linux I use gitflow and gitversion. The former helps me with branch and tags management, the latter keep tracks of the semantic version in a semi-automatic fashion (given a branch/commit/tag it generate a semver automatically based on the repo log). Gitflow should be supported by GUI tools too, but I'm more a CLI guy.

I’m not sure about in Bitbucket, but our pipeline has installed GitVersion which ups the build version based on SemVer. https://gitversion.net/docs/ We have a HealthCheck endpoint to return this version.

I know that GitVersion exists, which I think can automatically calculate the version number for me. But it's not entirely clear to me that it will do this. Also it doesn't seem to have a nbgv set-version equivalent that will just create a tag based on the calculated version number.

Kind of like you mention though, I tend to still create a build script using gitversion then just have the GitHub Action kick off the script. I find value in being able to create artifacts on a developer machine so having a simple script to run makes that as painless as possible and when I last looked a year or so ago there wasn't a good way of running GitHub Actions on your development machine.

Self promotion: I made Verlite for this purpose, tho something like GitVersion might be more suitable for your workflow.