[
https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira...
]
Barak Korren commented on OVIRT-758:
------------------------------------
Building and publishing Docker images should be quite simple to do from std-ci.
There is no technical reason why this couldn`t be done directly in VDSM's
check-patch.sh or build-artifacts.sh. But maybe mock will require some tweaking.
But perhaps the docker files shouldn't be in the vdsm repo for the sake of not
building them unnecessarily, this can also be avoided with a simple condition in the
script file though.
Vdsm docker testing images
--------------------------
Key: OVIRT-758
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-758
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
Hi all,
Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images.
See
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic...
Currently I maintain the images in docker hub:
-
https://hub.docker.com/r/nirs/vdsm-centos/
-
https://hub.docker.com/r/nirs/vdsm-fedora/
I configured automatic build, so each time I push a change to this branch:
https://github.com/nirs/vdsm/tree/dockerfile
Docker go and rebuilds the images.
We want to move the images to docker hub ovirt account:
https://hub.docker.com/u/ovirt/
And configure vdsm github project so docker will rebuild
the images when we push a changes to the dockerfile branch,
or another solution to allow easy update of the images by
merging a new dockerfile.
Nir
--
This message was sent by Atlassian JIRA
(v1000.482.3#100017)