-
Notifications
You must be signed in to change notification settings - Fork 110
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
Run unit tests #283
Comments
Would this be a prow change for the plumbing job? |
We should use tekton for this (aka no prow, but adding something to our dogfooding setup) /cc @afrittoli |
Probably a Tekton pipeline that runs all the different unit tests in parallel would be nice. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
automation for these tests is still important /remove-lifecycle rotten |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
/cc @afrittoli Is it done now ? |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Expected Behavior
Unit tests for components that live in plumbing, such as https://github.com/tektoncd/plumbing/tree/master/buildbot, should be run on every PR and block merging.
Actual Behavior
#281 adds unit tests for the buildbot but nothing runs them.
Additional Info
Depends on #281 (which adds the tests!)
The text was updated successfully, but these errors were encountered: