CI: Connector Release

[piyushsingariya]

Driver/Adapter Release (Stable/Edge both release supported) (ARM/AMD)

Two Release channels

• stable means sanity of connector not having any experimental changes; and are released after thorough testing.

  • Versions follows the pattern stable-vX.x.x

• edge releases are completely exprimental, are used to release a connector image faster. Specially used in cases where testing extends to a production environment against a real world use-case. This release strategy helps maintaining a sanity for stable release

  • Version follows the pattern edge-{ULID}-{first_8_letters_of_the_commit}
  • ULID helps in determining the sequentiality of releases and commit help in identifying exactly

• Release via tags (Stable Release)

  • Tag pattern driver-{name}/vX.x.x; strict pattern no rc release supported
  • Tag driver-{name}/vX.x.x translates to stable-vX.x.x for example tag driver-postgres/v0.0.1 will generate docker images dhid/driver-postgres:stable-v0.0.1
  • Connector Release must not publish any Go package
  • Connector Release Changelog must only contains the respective connectors's changes

• Release via Workflow Trigger

  • Publishes edge images from branches/forks as well; Can only be triggered by Maintainers
  • Docker images tag translates to dhid/driver-postgres:edge-{ULID}-{first_8_letters_of_the_commit}

[piyushsingariya]

Every driver folder is supposed to have build.yml, contains basic outline for building docker image, if not docker image can be built directly. Docker image is built in 2 stages, build and final. if c support is required cgo_enabled is marked true.

Example build.yml

build:
  dependencies:
    - build-base
    - lzo-dev
  cgo_enabled: true
final:
  dependencies:
    - build-base
    - lzo-dev