ko VS GitVersion

Apko leverages the APK package format from Alpine and draws inspiration from ko, a fast container image builder for Go applications.

- There're many resources available about containerizing an application, but I suggest you buildpacks or ko, which doesn't require writing a Dockerfile

ko

You don't need to write and manage Dockerfiles. Simply just use ko: https://github.com/google/ko (You also don't need Docker Engine)

Or don't write a Dockerfile at all, and use ko: https://github.com/google/ko

Here is link number 1 - Previous text "ko"

It depends on your use case, but have you ever tried google/ko?

If you're using Go, I recommend https://github.com/google/ko (shameless plug), or for Java, use Jib.

I would recommend Google Ko if you are packaging Go apps: https://github.com/google/ko

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.