Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provide fully equipped release candidate of chectl and che-operator for pre-release testing

See original GitHub issue

Is your enhancement related to a problem? Please describe.

During pre-release testing of Eclipse Che, QE team is usually testing eclipse/che-server:rc image being installed by the command of chectl from --channel=next:

./install_chectl.sh --channel=next
  /usr/local/bin/chectl server:start \
    --platform=minikube \
    --cheimage=eclipse/che-server:rc

In this case only che-server is of pre-release version. Other artifacts like chectl, che-theia, che plugins are of next/latest versions, instead of release candidates.

Describe the solution you’d like

We can have --channel=rc of chectl, which will install Eclipse Che, and start workspaces by using release candidates of che-server, che-theia, che plugins etc by default.

References

https://github.com/eclipse/che/issues/14650

Issue Analytics

State:
Created 4 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

2reactions

tolushacommented, Mar 30, 2020

@nickboldt We don’t need RC anymore, right?

0reactions

nickboldtcommented, Apr 1, 2020

From @tolusha 👍

There is misunderstanding. We already have script to generate PR for operator hub https://github.com/eclipse/che-operator/blob/master/olm/prepare-community-operators-update.sh

Top Results From Across the Web

Release 7.2.0 · Issue #14650 · eclipse/che · GitHub

Release PR Release 7.2.0 version of che-plugin-registry ... Provide fully equipped release candidate of chectl and che-operator for pre-release testing # ...