OpenEBS Jenkins CI must trigger on Pull Request.
Opened this issue · 1 comments
yudaykiran commented
Currently the CI Performs tests after merging the changes. A workflow for pull request has to be implemented.
ksatchit commented
As per some initial brainstorming, it would be better to perform a "quick-test" suite by including the proposed changes in PR on a local setup. This is referenced and addressed in the issue #363
The "quick-test" should essentially be a glorified/integrated version of the tests that are run today by travis for separate images like jiva, maya-apiserver etc.., Tests from label : area/maya kind/e2e are a good candidate to run.