Create 'master', 'nightly', 'release' CI for 'che-machine-exec' plugin and move images to quay.io
See original GitHub issueIs your task related to a problem? Please describe.
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/
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Getting Started with Quay.io
Sign into Quay.io. To sign into Quay.io, execute the docker login quay.io command: Note: If you go to your Quay account settings you...
Read more >Can't modify CHE_PROJECTS_ROOT env value through devfile
I made those changes as I'm using custom docker images. I don't think that it can be the source of the problem as...
Read more >How to get started with Quay Container Registry - YouTube
There is no functional Kubernetes cluster without a registry. If your registry is dead your OpenShift cluster is hosed.
Read more >Use Project Quay
Project Quay container image registries let you store container images in a central location. As a regular user of a Project Quay registry,...
Read more >eclipse/che 7.30.0 on GitHub - NewReleases.io
[Selenium] Stabilize devworkspace happy-path test #19710; Nightly Che Server build is broken #19699; Run Openshift CI in chectl release branches as che-operator ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@vparfonov @l0rd I would propose to use quay.io for
7.2.0
release and deprecate the docker one for che-machine-execI would propose the following CI / tags:
master
- CI is triggered onmaster
commits and tags based on the git commit hash & pushes to quay.ionightly
- CI is triggered from themaster
branch on a daily basis and pushesnightly
images to quay.iorelease
- CI is triggered from therelease
branch, tags images based on theVERSION
file e.g7.2.0
and pushes images toquay.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.