Semantic versioning, automatic creation of git tags, version strategies, etc.

  • Publishing git tags for Maven projects in Bitbucket Pipelines

    Update 2018-11-24: I’ve put together a maven plugin that can also publish git tags in Bitbucket Cloud, plus it checks there are no gaps in a semver sequence. It’s available here.

  • Slim GitVersion Docker image

    In a previous post, I wrote about GitVersion. GitVersion is a tool which solves semantic versioning of a git repository in its own way. With GitVersion, the version of any git repository is a pure function of its state, derived by tags, branches and commit messages.

  • Waiting for the correct version after deployment

    In this post, I’ll implement a post deployment check that waits until the application is running with the expected version. The first step is to make the application aware of its version. The easiest way to do that in our setup is with an environment variable. We’ll modify the deployment template of the Helm chart:

  • One script to version all

    This is just a fun hacking post. I put together a script that is able to handle all versioning strategies that I mentioned about in the post about versioning.

  • Semantic versioning with GitVersion

    I recently stumbled upon a tool called GitVersion which takes a different approach on versioning. I already mentioned some options regarding versioning, but all of them require you to actively specify the version somewhere. GitVersion instead is able to calculate it based on the state of your git repository.

  • On versioning

    According to Wiktionary, the word version means “a specific form of variation of something”. In computing, it’s “a particular revision of something” (e.g. software). The word has French and Latin roots. The Greek translation, έκδοση, can also be translated as publication.

  • Automatic versioning of npm packages

    When you are the maintainer of an npm package, you need to do some administrative work around its versioning. When you release a new version, you need to make sure the package.json is updated, the package is correctly uploaded to npm registry, the git repository is tagged accordingly and so on. You shouldn’t be doing these things manually if you can automate them.

  • Versioning Deployed Web Applications

    In this post, I’m going to discuss the setup I have for deploying an ASP.NET application in Linux.

This site uses third party cookies from Google Analytics and Google AdSense Accept and close popup