Skip to content

Discuss versioning of images and branching model #13

@cleverer

Description

@cleverer

Optimally, wed have the following scenario:

  • latest gets rebuilt daily/regularly
  • when a new release gets done, the tests are part of the acceptance tests.
  • By default, the compose file and the CI would run against the latest tagged release.
  • The docker build pipeline would run the tests against master and only build the image, if the tests succeed
  • This would allow for a pull request to master, to update the versioned default docker images. When that gets merged, the resulting merge commit gets tagged with that version, which creates the docker image with this version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions