Skip to content

Enable e2e testing for NATSS#1126

Merged
knative-prow-robot merged 6 commits into
knative:masterfrom
chizhg:EnableTestsForNatss
Apr 30, 2019
Merged

Enable e2e testing for NATSS#1126
knative-prow-robot merged 6 commits into
knative:masterfrom
chizhg:EnableTestsForNatss

Conversation

@chizhg
Copy link
Copy Markdown
Contributor

@chizhg chizhg commented Apr 30, 2019

Proposed Changes

  1. Clean up e2e-tests.sh a little bit.
  2. Enable e2e testing for natss

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Apr 30, 2019
@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 30, 2019
@chizhg
Copy link
Copy Markdown
Contributor Author

chizhg commented Apr 30, 2019

/uncc @matzew
/uncc @grantr

@chizhg
Copy link
Copy Markdown
Contributor Author

chizhg commented Apr 30, 2019

/cc @Abd4llA
/cc @adrcunha

Comment thread test/e2e-tests.sh
Comment thread test/e2e-tests.sh Outdated
Comment thread test/e2e-tests.sh
}

# Create resources required for NATSS provisioner setup
function natss_setup() {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

should this be in a separate script ? I assume this file can become messy w/ future addons, like for Kafka.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 for moving support functions to a separate file. But this can be done in a separate PR IMO.

@chizhg chizhg changed the title Enable e2e testing for natss Enable e2e testing for NATSS Apr 30, 2019
@matzew
Copy link
Copy Markdown
Member

matzew commented Apr 30, 2019

@Fredy-Z should this be instead done on the to be renamed eventing-contrib folder ?
/cc @n3wscott

@adrcunha
Copy link
Copy Markdown
Contributor

/approve
/lgtm
/hold

Holding in case you want to address the concern from Matthias.

@knative-prow-robot knative-prow-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Apr 30, 2019
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrcunha, Fredy-Z

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

The pull request process is described here

Details 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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2019
@matzew
Copy link
Copy Markdown
Member

matzew commented Apr 30, 2019 via email

@matzew
Copy link
Copy Markdown
Member

matzew commented Apr 30, 2019 via email

@chizhg
Copy link
Copy Markdown
Contributor Author

chizhg commented Apr 30, 2019

/hold cancel

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 30, 2019
@knative-prow-robot knative-prow-robot merged commit 3546f63 into knative:master Apr 30, 2019
@matzew
Copy link
Copy Markdown
Member

matzew commented Apr 30, 2019 via email

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. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants