gitversion | A helper for bumping versions via git tags | Build Tool library

As one of the maintainers of GitVersion, I'm obviously biased, but since you're asking how to use GitVersion to implement a "best practice for automated software release", I'm going to unashamedly give you a textual description of a talk I've done on how I prefer to version and release software with GitVersion, TeamCity and Octopus Deploy.

The first thing you should figure out is what kind of developer workflow you want for your software. GitVersion supports Git Flow and many simplified variants of it, and GitHub Flow (as well as many other trunk based development flows). Which workflow you should choose depends on what type of software you are developing, your team and most importantly; your personal preference.

Once you have chosen your workflow, you can configure which mode GitVersion should operate under.

GitVersion works by calculating a version number from your Git repository. This means that you should not commit a version number to Git in any shape or form. Not within a package.json, pom.xml, .csproj, or any other build- or project-related file that often mandates the existence of a version number.

Instead, you should allow GitVersion to produce a version number based on the Git history, using the currently checked out commit as its starting point, and searching through the parents and their tags to calculate an appropriate version number for the current commit. This version number can then be used in any way you want in your build pipeline. You can, for instance, write GitVersion's FullSemVer variable to package.json by executing the following command:

I have the same problem

You're using aws-iam-authenticator 0.5.5, AWS changed the way it behaves in 0.5.4 to require v1beta1.

It depends on your configuration, but you can try to change the K8s context you're using to v1beta1

Otherwise switch back to aws-iam-authenticator 0.5.3 - you might need to build it from source if you're using the M1 architecture as there's no darwin-arm64 binary built for it

I recommend using az login An auth token is cached locally on your environment and should give you access to your Kubernetes cluster.

Then follow the Microsoft docs to install kubectl.

The kubectl version error helped : Unable to connect to the server: dial tcp i/o time out

It seems I had already played with k8s :

Please use following command in pipeline.yaml hope it should work.

Secret ... is invalid: data: Too long: must have at most 1048576 bytes

This is a well known limitation of Kubernetes secrets (version 1.23 at the moment). The official k8s documentation says:

Individual secrets are limited to 1MiB in size. This is to discourage creation of very large secrets which would exhaust the API server and kubelet memory. However, creation of many smaller secrets could also exhaust memory. More comprehensive limits on memory usage due to secrets is a planned feature.

So, first of all, check if some unnecessary files/dirs are stored in your chart directories and remove them. I am sure you have already removed all unnecessary files.

Using such a storage backend is particularly useful if your release information weighs more than 1MB (in which case, it can't be stored in Secrets because of internal limits in Kubernetes).

To enable the SQL backend, you'll need to deploy a SQL database and set the environmental variable HELM_DRIVER to sql. The DB details are set with the environmental variable HELM_DRIVER_SQL_CONNECTION_STRING.

You can set it in a shell as follows:

Thanks to RadekW, the problem is now solved. The path should be written as /run/desktop/mnt/host/c/PATH/TO/FILE, and in my case: /run/desktop/mnt/host/c/temp/testfiles. If I find any documentation about this, I will add a source.

based on the iconic Failed to create SSL Connection output in the logs, I assume that you have run into the dreaded The demo certificates included in the Hono chart have expired problem.

The Cloud2Edge package chart is being updated currently (https://github.com/eclipse/packages/pull/337) with the most recent version of the Ditto and Hono charts (which includes fresh certificates that are valid for two more years to come). As soon as that PR is merged and the Eclipse Packages chart repository has been rebuilt, you should be able to do a helm repo update and then (hopefully) succesfully install the c2e package.

Read carefully and understand at least part of GitVerson docs (paragraphs 1+2)

The shortest possible extraction

GitVersion will increment the metadata for each build so you can tell builds apart. For example, 1.0.0+5 followed by 1.0.0+6. It is important to note that build metadata is not part of the semantic version; it is just metadata!