Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix getting-started triggers #642

Merged
merged 1 commit into from
Jul 1, 2020
Merged

Fix getting-started triggers #642

merged 1 commit into from
Jul 1, 2020

Conversation

dibyom
Copy link
Member

@dibyom dibyom commented Jun 26, 2020

Changes

The EventListener was referring to the Binding via name instead of ref. Also, run the getting-started examples as part of the e2e YAML tests. While this won't catch all issues with the examples, it should catch obvious syntax issues like this one.

Fixes #639
Fixes #164

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

/kind bug

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 26, 2020
@tekton-robot tekton-robot requested review from dlorenc and ncskier June 26, 2020 19:00
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 26, 2020
@@ -1,4 +0,0 @@
apiVersion: v1
kind: Namespace
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deleted this -- the docs explicitly mention creating the namespace. The formerly commented out test was using this. I replaced it with a call to create the namespace in the test script.

@tekton-robot tekton-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 29, 2020
The EventListener was referring to the Binding via `name` instead of `ref`.
Also, run the getting-started examples as part of the e2e YAML tests. While
this won't catch all issues with the examples, it should catch obvious syntax
issues like this one.

Fixes tektoncd#639
Fixes tektoncd#164

Signed-off-by: Dibyo Mukherjee <dibyo@google.com>
@wlynch
Copy link
Member

wlynch commented Jun 30, 2020

/lgtm /approval

@wlynch
Copy link
Member

wlynch commented Jun 30, 2020

/lgtm
/approval

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 30, 2020
@iancoffey
Copy link
Member

/lgtm

@wlynch
Copy link
Member

wlynch commented Jul 1, 2020

/approve

@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wlynch

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 1, 2020
@tekton-robot tekton-robot merged commit 0fd1938 into tektoncd:master Jul 1, 2020
AlanGreene added a commit to AlanGreene/website that referenced this pull request Jul 15, 2020
Some of the Triggers content was moved in tektoncd/triggers#642,
specifically: create-ingress.yaml and create-webhook.yaml

These have been moved to the getting-started folder which broke
the website sync script, blocking other changes.

Update the sync config to point to the new paths to unblock
other changes.
tekton-robot pushed a commit to tektoncd/website that referenced this pull request Jul 20, 2020
Some of the Triggers content was moved in tektoncd/triggers#642,
specifically: create-ingress.yaml and create-webhook.yaml

These have been moved to the getting-started folder which broke
the website sync script, blocking other changes.

Update the sync config to point to the new paths to unblock
other changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to create Event Listener without ref and spec included in YAML. Fix or delete E2E Docs Tests
5 participants