Skip to content

Fix for using 'dev' images in development, instead of 'latest'.

Kostas FILIPPOPOLITIS requested to merge fix/MIP-580/dev_mipengine_releases into master

Created by: ThanKarab

Changelog:

  • Fix for using 'dev' images in development, instead of 'latest'. Jira

Explanation and solution: The problem we had previously was that component version were never published other than production releases.

This meant that a developer would need to 1) build the images that he used in his current branch or 2) use the “latest” production releases.

In the 1st option it would mean more manual work and in the 2nd option, which we did now, before a monthly release components would slowly become out of date with the master branch.

The solution implemented was to:

  • Separate the “latest” tag that is used for production from a “dev” tag that we will use in development. So currently in the .deployment.toml all images have a “dev” tag.
  • When a PR is merged github actions run publishing all components to that “dev” tag, which means that the “dev” tag will always have the latest master merged versions.

Merge request reports