[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23608#comment-23608 ] Barak Korren commented on OVIRT-890: ------------------------------------ It shouldn't really matter _where_ we publish. As I see it there are two main option to publish _anything_ from standard CI: # Have build_artifacts.sh put it in "exported_artifacts" and then have "the system" publish it to where it needs to go - this is what the experimental flow is doing for example for RPMs. # Publish directly from build_artifacts.sh It should be obvious that solution #2 is more flexible and will require less maintenance from us in the long run, but it has a couple of issues: # For publishing typically some credentials are needed # The decision where to publish ends up being made at the discretion of the developer, as opposed to on an environment level. I don't think #2 is really an issue. WRT #1, this is something we've encountered before, and perhaps we should solve it by adding support for credentials and secrets in Standard CI (OVIRT-894).

Add support to publish containers in standard CI ------------------------------------------------

Key: OVIRT-890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra Labels: containers, docker, standard-ci

Mostly likely to Dockerhub or OpenShift registry. We'll need a pet project to try out the various options.

-- This message was sent by Atlassian JIRA (v1000.606.0#100023)