exasol/release-droid

Enhanced support for golang releases - Create multiple git tags

ckunki opened this issue · 0 comments

ckunki commented

Currently RD generates only a single tag e.g. with version "1.2.3".
However Golang requires different tag conventions.

The current ticket proposes to analyze file .project-keeper.yml and to identify and support different scenarios as described below.

For Go projects

  • version numbers exist only in git tags.
  • project keeper should read version number from file .project-keeper.yml, e.g.
sources:
  - type: golang
    path: go.mod
version: 0.1.0
  • RD reads version number from file doc/changelog.md
  • Version number should always be without any prefix. PK and RD should take care of creating correct git tags

Scenarios and rules

  • Case (C1): File .project-keeper.yml contains Go module in root folder (path: go.mod)
    • Create git tag v1.2.3
    • Ignore other source modules
  • Case (C2): All other cases
    • Create git tag 1.2.3

Additional option (O): For each go module in a subfolder contained in file .project-keeper.yml (e.g. path: subfolder/go.mod)

  • create an additional git tag subfolder/v0.2.3

Examples

extension manager - Case (C1)

sources:
  - type: golang
    path: go.mod

exasol-test-setup-abstraction-server - Combination of Case (C2) and Option (O)

sources:
  - type: maven
  - type: golang
    path: go-client/go.mod

Observation: The tags of exasol-test-setup-abstraction-server currently contain multiple variants, e.g. 0.2.3, go-client/v0.2.3, 0.2.0, v0.2.0.
This requires the sorting for existing tags in com.exasol.releasedroid.adapter.repository.Version to be aware of potential prefixes "v" and ".*/".

See also