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

Only run [PR-Blocking] tests for PRs #242

Closed
jamiemonserrate opened this issue Nov 15, 2021 · 3 comments · Fixed by #245
Closed

Only run [PR-Blocking] tests for PRs #242

jamiemonserrate opened this issue Nov 15, 2021 · 3 comments · Fixed by #245
Assignees

Comments

@jamiemonserrate
Copy link
Contributor

Describe the solution you'd like
We should only run the [PR-Blocking] tests as part of each PR. This will help improve the feedback time to folks raising PRs.

We should also have the ability to run the rest of the suite on demand. Preferably via github /commands

@karuppiah7890
Copy link

karuppiah7890 commented Nov 15, 2021

For K8s Prow like /command in GitHub, you could checkout https://github.com/jpmcb/prow-github-actions which is something we use for labelling issues primarily. You could checkout how it can be used to run test suites on GitHub Actions

@anusha94
Copy link
Contributor

Thanks @karuppiah7890 for the pointer. @shamsher31 , is this something we can investigate for this project?

@shamsher31
Copy link
Contributor

For K8s Prow like /command in GitHub, you could checkout https://github.com/jpmcb/prow-github-actions which is something we use for labelling issues primarily. You could checkout how it can be used to run test suites on GitHub Actions

This looks great. Thanks for sharing @karuppiah7890 .

@shamsher31 , is this something we can investigate for this project?

We can use it for now until Prow is available across Tanzu projects.

@shamsher31 shamsher31 self-assigned this Nov 16, 2021
This was referenced Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants