You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This is currently work in progress:  FINCN-170 - Getting issue details... STATUS INFRA-18516 - Getting issue details... STATUS


How to run fineract-cn public Docker images


There are public repositories in DockerHub for fineract-cn: 

Micro serviceApache URL Temporary URL for setting up (this column be deleted once the job is completed)





https://cloud.docker.com/repository/docker/aasaru/fineract-cn-provisioner



















Running a micro service public image

TODO - replace "aasaru" with "apache" once the set-up has been completed

docker run aasaru/fineract-cn-provisioner:latest

Or if you want to run specific version

docker run aasaru/fineract-cn-provisioner:version-number-goes-here


You need to generate keys and pass them to docker images as environmental variables. See these instructions.

How the Docker Hub has been set up



Autobuild has been configured for these repositories with following setup:

  • pushing to branch "develop" - triggers a build and publishes to "latest"
  • tagging a version - triggers a build and publishes it as a version:
    • if the tag has a form "numbers.and.dots-RELEASE" (case insensitive) then the docker tag will be "release-numbers.and.dots"
      • example: 1.2.3-RELEASE becomes "release-1.2.3"
      • example: v-1.2.3 - nothing is triggered as only numbers and dots are allowed
    • if the tag has a form "numbers.and.dots" then docker tag will be: "numbers.and.dots"
      • example: 1.2.3 becomes "ver-1.2.3"
  • pushing to any other branch besides "develop" - nothing is triggered and no images are built


For autobuild to work the Dockerfile of each  has been split into two stages:

  • build stage - builds the jar. Only the jar is passed to the run stage.
  • run stage - runs the jar
  • No labels