Skip to content
New issue

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

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

Already on GitHub? # to your account

OpenEBS Jenkins CI must trigger on Pull Request. #55

Open
yudaykiran opened this issue Sep 8, 2017 · 1 comment
Open

OpenEBS Jenkins CI must trigger on Pull Request. #55

yudaykiran opened this issue Sep 8, 2017 · 1 comment
Milestone

Comments

@yudaykiran
Copy link
Contributor

Currently the CI Performs tests after merging the changes. A workflow for pull request has to be implemented.

@ksatchit
Copy link
Contributor

ksatchit commented Oct 3, 2017

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.

sachinmukherjee referenced this issue in sachinmukherjee/openebs Nov 13, 2018
@kmova kmova transferred this issue from openebs/openebs Mar 13, 2019
@kmova kmova added this to the GA-Backlog milestone Mar 13, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants