DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
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 service | Apache 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 to follow the same principles as already used with publishing to JFrog Artifactory - this means that one can trigger a build by pushing to branch "develop" and by creating a release (tag) in Github. The only exception is that pushing to other branches besides "develop" doesn't trigger creating image in Docker Hub.
Dockerhub autobuild configuration:
Docker Tag | Source | Comment |
|---|---|---|
| latest | develop | Every push to "develop" branch is built and published under tag "latest". |
release-{sourceref} | /^REL([0-9.]+)$/ | Without this configuration Docker Hub doesn't work. No build should actually trigger this. |
{\1}-{\2} | /^([0-9.]+)-([0-9A-Za-z.]+)$/ | Releases like "1.3.5-M.1", "1.5.7-RC.1", "1.5.7.1-RC.1" and "2.0.0-RELEASE" |
{\1}.{\2}.{\3} | /^([0-9]+)\.([0-9]+)\.([0-9]+)$/ | Releases like "2.0.0" |
For autobuild to work the Dockerfile of each repository 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 built