[MXS-2912] Take ownership of all MaxScale Docker images Created: 2020-03-03 Updated: 2020-11-24 Resolved: 2020-11-24 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Packaging |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | 2.4.15 |
| Type: | Task | Priority: | Major |
| Reporter: | Todd Stoffel (Inactive) | Assignee: | Timofey Turenko |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Epic Link: | General MariaDB Docker Image |
| Sprint: | MXS-SPRINT-102, MXS-SPRINT-103, MXS-SPRINT-104, MXS-SPRINT-105, MXS-SPRINT-106, MXS-SPRINT-107, MXS-SPRINT-108, MXS-SPRINT-109, MXS-SPRINT-110, MXS-SPRINT-119, MXS-SPRINT-120 |
| Description |
|
The MaxScale team will take ownership of: https://github.com/mariadb-corporation/maxscale-docker and https://hub.docker.com/repository/docker/mariadb/maxscale It has been decided by company executives that the product teams will own their respective Docker images. There should be no updates to these images without MaxScale product management approval. |
| Comments |
| Comment by Julien Fritsch [ 2020-04-09 ] |
|
Just an idea, but since abychko will be doing for both the Community Server and Enterprise Docker images, maybe we can go and automate/do it for MaxScale too? |
| Comment by Timofey Turenko [ 2020-07-23 ] |
|
now the task "Create Docker Maxscale image" is implemented in the Maxscale BuildBot. Image goes to the own Docker registry |
| Comment by Timofey Turenko [ 2020-11-04 ] |
|
a new implementation of Docker file https://github.com/mariadb-corporation/maxscale-docker/blob/centos8tools/maxscale/Dockerfile - based on CentOS8 and the possibility to create CI version of the images. next task: add BB task. |
| Comment by Timofey Turenko [ 2020-11-24 ] |
|
BB generates CI Docker images for all calls of "build_maxscale_all" task and puts them into our own Docker registry |