[JIRA] (OVIRT-1390) Implement "archive-artifacts" flow for containers in STD-CI

[Barak Korren (oVirt JIRA)]

     [ https://ovirt-jira.atlassian.net/browse/OVIRT-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barak Korren updated OVIRT-1390:
--------------------------------
    Description: 
This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKDeG5rXBVXgSaHHQfvZ1la41E/edit?usp=sharing] flow implementation process.

We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI.

The design as as following:
# An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag.
# After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtinfra" account on DockerHub.
# The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL)
# The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin)

  was:
This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKDeG5rXBVXgSaHHQfvZ1la41E/edit?usp=sharing] flow implementation process.

We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI.

The design as as following:
# An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag.
# After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtci" account on DockerHub.
# The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL)
# The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin)


> Implement "archive-artifacts" flow for containers in STD-CI
> -----------------------------------------------------------
>
>                 Key: OVIRT-1390
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1390
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: Jenkins
>            Reporter: Barak Korren
>            Assignee: infra
>            Priority: High
>              Labels: standard-ci
>
> This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKDeG5rXBVXgSaHHQfvZ1la41E/edit?usp=sharing] flow implementation process.
> We want to implement functionality similar to what "archive-artifacts" gives use for regular files, for containers in standard-CI.
> The design as as following:
> # An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag.
> # After the STD-CI script finishes successfully, the CI system will take the tagged container images and push them the the "ovirtinfra" account on DockerHub.
> # The CI system will tage pushed images with the SHA1 hash of the URL of the Jenkins job build that built the image (Can be found in $BUILD_URL)
> # The CI system will output examples for '{{docker pull}}' and '{{docker run}}' command that would be needed to obtain the build image to the build status screen (Using the Groovy post-build plugin)



--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)