Create 'master', 'nightly', 'release' CI for 'che-machine-exec' plugin and move images to quay.io.
This is already done for plugin and devfile registries - https://quay.io/organization/eclipse
Currently, for machine-exec there is only codenvy 'release' CI that should be decommissioned - https://ci.codenvycorp.com/view/release/job/release-che-machine-exec-plugin/
cc: @vparfonov @AndrienkoAleksandr are you ok with this approach? Might be wrong, but AFAIK there is no other CI that https://ci.codenvycorp.com/view/release/job/release-che-machine-exec-plugin/ for the machine-exec plugin
@ibuziuk I am OK with this approach.
@AndrienkoAleksandr am I correct that https://ci.codenvycorp.com/view/release/job/release-che-machine-exec-plugin/ is the only CI for machine-exec atm ?
@AndrienkoAleksandr am I correct that https://ci.codenvycorp.com/view/release/job/release-che-machine-exec-plugin/ is the only CI for machine-exec atm ?
Yes, you are right.
I would propose the following CI / tags:
master - CI is triggered on master commits and tags based on the git commit hash & pushes to quay.ionightly - CI is triggered from the master branch on a daily basis and pushes nightly images to quay.iorelease - CI is triggered from the release branch, tags images based on the VERSION file e.g7.2.0 and pushes images to quay.io@vparfonov @AndrienkoAleksandr I do not think other tags are needed like e.g. next 7.0.0-next that present in https://hub.docker.com/r/eclipse/che-machine-exec/tags
If those are needed please clarify the use-case.
PR for creating CI jobs - https://github.com/openshiftio/openshiftio-cico-jobs/pull/1073
quay.io repo - https://quay.io/repository/eclipse/che-machine-exec
@vparfonov @l0rd I would propose to use quay.io for 7.2.0 release and deprecate the docker one for che-machine-exec
PRs are merged. Closing
Most helpful comment
@vparfonov @l0rd I would propose to use quay.io for
7.2.0release and deprecate the docker one for che-machine-exec