search

openshift / pipelines-tutorial

A step-by-step tutorial showing OpenShift Pipelines
Apache License 2.0
298 stars 619 forks source link

README suggests try.openshift.com, but users cannot install operators #152

Closed ktdreyer closed 2 years ago

ktdreyer commented 2 years ago

When I go to try.openshift.com, my user account is named DevSandbox. This user does not appear to have permissions to install operators, so I cannot proceed with the pipelines tutorial in this environment.

Is there another way to get administrator access to the try.openshift.com environments, or some other clues we could give users in the README?

nikhil-thomas commented 2 years ago

hi, at present OpenShift Pipelines Operator is not supported on try.openshift.com. Let me try to help you with the 2nd question.

or some other clues we could give users in the README?

@siamaksade @vdemeester

@ktdreyer feel free to reach us on tektoncd-pipeline-devchannel on coreos slack. 🧑‍💻

ktdreyer commented 2 years ago

Thanks.

Should we remove all try.openshift.com references in this tutorial, then?

What would you recommend instead?

vdemeester commented 2 years ago

Note that it doesn't work with the "Developer sandbox" (first box) but it should work with the other options (Managed Services and Self-Managed). We may want to add in the README that it doesn't run on "Developer sandbox" (yet).

openshift-bot commented 2 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 2 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 2 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci[bot] commented 2 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/pipelines-tutorial/issues/152#issuecomment-1125994883): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.