[FOLIO-916] Test docker image builds in Jenkins Created: 27/Oct/17 Updated: 12/Nov/18 Resolved: 20/Nov/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint25, sprint26 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 day, 3 hours | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
Docker has a simple health check facility for verifying the basic health of an application running inside a container. Utilize the health check facility to test docker images built by Jenkins before publishing to docker repository. |
| Comments |
| Comment by John Malconian [ 27/Oct/17 ] |
|
Implemented Docker image testing for Okapi CI. The image starts in a container and verifies that Okapi has started in 'dev' mode by checking the /_/proxy/health endpoint. Need to determine a suitable endpoint in each back end module before implementing this across additional FOLIO modules. |
| Comment by John Malconian [ 20/Nov/17 ] |
|
Implemented container tests in Jenkins CI by utilizing docker 'health checks' options. All raml-based backend modules utilize the /apidocs endpoint to verify that the application is running inside the container. A rather simple test, but sufficient for now. Specific health checks can be enabled on a per project basis using the 'healthChk' and 'healthChkCmd' options in the Jenkinsfile. Will discuss separately adding a standard endpoint across all modules. |