PoC for hosted development environment for FOLIO teams
(FOLIO-2601)
|
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | PoC for hosted development environment for FOLIO teams |
| Type: | Task | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | dev-environment | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps: sprint 92 |
| Development Team: | FOLIO DevOps |
| Epic Link: | PoC for hosted development environment for FOLIO teams |
| Description |
|
Stanislav Miroshnichenko reports that Rancher pipeline is unable to deploy Docker artifacts via Helm that have been pushed to the default Rancher docker registry from same pipeline. If no work around is viable, we will need to store these docker artifacts in a separate docker registry, ideally one that will automatically purge older artifacts since they will quickly pile up. We can possibly enable the docker registry feature of our existing Nexus repository for this. CC: jroot |
| Comments |
| Comment by John Malconian [ 06/Jul/20 ] |
|
I set up a hosted Docker registry on our existing FOLIO Nexus repository - The registry is located at 'docker.dev.folio.org'. Authentication is required to push images to the registry No authentication should be necessary to pull images from the registry. The registry has a daily image clean up task that delete images that haven't been downloaded in the last 20 days. |