CI/CD should apply release tags to images in Docker Hub

Description

When we release any versions of OpenLMIS (3.0.0-beta, 3.1.2, etc), we want each openlmis image in Docker Hub to be tagged with a tag that matches our release tag. This should happen on each image we publish there (eg, look under the Releases tab of each repository, eg https://github.com/OpenLMIS/openlmis-requisition/releases).

We expect that Jenkins might need some input/trigger in order to know that a release tag exists and to decide to publish a set of Docker Hub images with that tag. For example, perhaps we tell one or more Jenkins job to build and publish a new release tag ('3.1.2-rc1') and that causes Jenkins to build each repo and publish each image to Docker Hub with that tag added.

Acceptance Criteria

  • Document in this ticket how this process will work.

  • Implement this into our Jenkins setup at build.openlmis.org.

  • Update the CI/CD documentation in the wiki.

  • Update the Rolling a Release wiki page.

Status

Assignee

Brandon Bowersox-Johnson

Reporter

Brandon Bowersox-Johnson

Labels

None

Sprint

None

Fix versions

Priority

Major