Each time when a developer change the core service version they need to update docker compose file in several repositories. For now there are four repositories: openlmis-contract-tests, openlmis-ref-distro, openlmis-reference-ui and openlmis-deployment. In the last repository the developer needs to update the docker files for each OpenLMIS server that use service SNAPSHOT version (currently there are too servers: test and perftest). This document will try to show solutions to the problem.

Single version file

With the 

Jira Legacy
server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-3316

 the openlmis-ref-distro repository has a single file that contain all service versions. Thanks that the developer does not need to find and update single row in docker-compose file (which is huge) but instead they need to update single line in very small file which content should be fully visible on the screen. Implementing this solution to other repositories should decrease time needed to find correct line in docker-compose file and for openlmis-deployment will decrease places that need update because when the developer update version servers will automatically retrieve correct version:

...

Disadvantage of this solution is that a developer still need to update service version in each repository each time when the service version will be changed. This solution only combine all pieces needed to updat in the given repository to a single place.

Script

The docker hub expose API that could be used to find and update service version in the given repository. To retrieve a list of all docker images we need to only send a request to the following URL. The important thing is that this endpoint is accessible for everyone. Authentication is not needed.

...