Identify and implement FOLIO software release process
(FOLIO-317)
|
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Identify and implement FOLIO software release process |
| Type: | Sub-task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 day, 4 hours | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
The hosted Docker registry functionality in Nexus just isn't cutting it. There is no easy way to expire/remove old images and disk utilization quickly becomes an issue. Therefore, we should probably utilize Docker Hub which is free for public repositories. |
| Comments |
| Comment by John Malconian [ 26/Sep/16 ] |
|
I've created an account called 'folio' on Docker Hub and created organizational namespaces called 'folioci' and 'folioorg'. We can, therefore, create repositories in any of these namespaces. I've modified Jenkins jobs for several FOLIO modules to build Docker images and publish them to the FOLIO CI namespace called 'folioci'. 'folioci' will be used primarily for publishing snapshot images for use for testing and CI. A list of the current docker repositories can be viewed at the following: https://hub.docker.com/u/folioci/dashboard/ Images for mod-circulation, mod-acquisitions, and mod-configuration have been published so far. Next step is to publish mod-auth modules and mod-metadata possibly. |
| Comment by John Malconian [ 27/Oct/16 ] |
|
Backend modules that have build jobs in Jenkins are now pushed to Docker Hub automatically to the 'folioci' Docker organization. https://hub.docker.com/r/folioci/ These repositories are meant to be used for further Jenkins integration testing, but are publicly accessible and available to everyone for FOLIO development and testing. Each repository could probably use additional usage documentation which could just be added to a 'Docker' section of the project's README on GitHub. |