search

openshift / pipelines-tutorial

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

Unable to create trigger #133

Closed jeffwarnica closed 2 years ago

jeffwarnica commented 3 years ago

[jwarnica@jwarnica crc-linux-1.22.0-amd64]$ oc create -f https://raw.githubusercontent.com/openshift/pipelines-tutorial/master/03_triggers/03_trigger.yaml Error from server (BadRequest): error when creating "https://raw.githubusercontent.com/openshift/pipelines-tutorial/master/03_triggers/03_trigger.yaml": admission webhook "webhook.triggers.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "ref"

OpenShift Version: 4.6.15 redhat-openshift-pipelines-operator.v1.2.3

san-biqmind commented 3 years ago

Please use the branch release-tech-preview-2 branch on OpenShift 4.6.x. The same has been referenced in the Red Hat documentation https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html-single/pipelines/index#installing-pipelines

I had the same issue using the master branch.

santhoshi@Azure:~$ oc create -f https://raw.githubusercontent.com/openshift/pipelines-tutorial/release-tech-preview-2/03_triggers/02_template.yaml triggertemplate.triggers.tekton.dev/vote-app created santhoshi@Azure:~$ oc create -f https://raw.githubusercontent.com/openshift/pipelines-tutorial/release-tech-preview-2/03_triggers/01_binding.yaml triggerbinding.triggers.tekton.dev/vote-app created santhoshi@Azure:~$ oc create -f https://raw.githubusercontent.com/openshift/pipelines-tutorial/release-tech-preview-2/03_triggers/03_event_listener.yaml eventlistener.triggers.tekton.dev/vote-app created santhoshi@Azure:~$ oc expose svc el-vote-app route.route.openshift.io/el-vote-app exposed

Tested on ARO (Azure Red Hat OpenShift): 4.6.17 redhat-openshift-pipelines-opertor.v1.2.3

openshift-bot commented 3 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 3 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/133#issuecomment-899944172): >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.