tarantool / tarantool / 36356683201

88%

push

github

build: support entrypointless versions for Alpine

TL;DR: Fix failures of an Alpine packaging workflow on `release/2.11` on
a dummy commit just after a release. The full story is below, if you're
curious.

The [release policy][policy] introduces an `X.Y.Z-entrypoint` tag to
mark a start of work on a major or minor release.

Say, we have some `A.B.*` releases and we start to work on `(A+1).0.0`
or `A.(B+1).0`. It carries `A.B.*` into a `git describe` based version,
while the branches are now disconnected: `A.B.*` may have its own
releases after the branch. Actually, that's how `2.11.*` and `3.*.*`
live: the latter had its first release a year or so after the branching.

So, the policy proposes a special marker for a start of a new major or
minor branch: `(A+1).0.0-entrypoint` and `A.(B+1).0-entrypoint`[^1]. A
maintainer creates an empty commit on `master` and places the tag on it.
(The old `A.*.*` (or `A.B.*`) release branch is forked before the empty
commit.)

As time went on, maintainers started to place `<...>-entrypoint` tags at
the start of work on a patch level release: once `A.B.C` is released,
`A.B.(C+1)-entrypoint` is set on the commit next to it. This is neither
forced nor prohibited by the policy. The original motivation from the
policy barely works here -- no branching happens -- but it adds a
feeling of consistency[^2].

However, the past entrypointless versioning schema stays, in a
rudimentary form.

Let's assume that `A.B.C` is just released and we push a dummy commit on
top of it to set `A.B.(C+1)-entrypoint` to it. This dummy commit is not
tagged yet and the `A.B.C` release tag is just behind it. So, here we
get the usual `A.B.C-1-g<hash>` git describe string instead of
`A.B.(C+1)-entrypoint-0-g<hash>`[^3].

Mostly, this exception doesn't hurt: Tarantool itself uses only
major/minor/patch, RPM/Deb packaging scripts work with either version
schema correctly.

However, the Alpine packaging script doesn't support the entrypointless
versio... (continued)

72391 of 121283 branches covered (59.69%)

108791 of 123751 relevant lines covered (87.91%)

1415816.4 hits per line