This is a part of containers CI/CD 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:

1. An STD-CI script that generated container images need to tag them with the "exported-artifacts" tag.

2. 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.

3. 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)

4. 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)