ci: add github action to trigger E2E #3468
Conversation
Madhu-1
added
ci/skip/e2e
Madhu-1
force-pushed
the
issue-commentor
branch
from
8b8035c
to
a62832e
Compare
Great, the label already exists! Thanks 👍 |
|
@nixpanic Lets manually merge this PR to get CI job started? |
Disable e2e tests by default in CI to save resources. cephcsi maintainers or contributors can add the ok-to-test label to trigger the e2e tests. depends on ceph#3468 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
| on: | ||
| pull_request_target: | ||
| types: | ||
| - labeled |
There was a problem hiding this comment.
can the ci/* branch(es) be excluded from this?
There was a problem hiding this comment.
also wondering if this can be triggered after a rebase and the label is set...
There was a problem hiding this comment.
Yes we can trigger only on required branches. for that we need to remove and re-add the label for now (we can see how that can be automated later?).
There was a problem hiding this comment.
updated to run on devel and release branch for now
Madhu-1
force-pushed
the
issue-commentor
branch
from
a62832e
to
05868d8
Compare
mergify
bot
dismissed
nixpanic’s stale review
Pull request has been modified.
Madhu-1
added
ok-to-test
Disable e2e tests by default in CI to save resources. cephcsi maintainers or contributors can add the ok-to-test label to trigger the e2e tests. depends on ceph#3468 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Disable e2e tests by default in CI to save resources. cephcsi maintainers or contributors can add the ok-to-test label to trigger the e2e tests. depends on #3468 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
based on the discussion on the slack channel. we are adding a github action to trigger the CI jobs when a ok-to-test label is added on the PR. This action is based on below github action https://github.com/peter-evans/create-or-update-comment Sample Demo avaiable at https://github.com/Madhu-1/ \label-commentor-action-testing/pull/4 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
Madhu-1
force-pushed
the
issue-commentor
branch
from
05868d8
to
c56e335
Compare
| with: | ||
| issue-number: ${{ github.event.pull_request.number }} | ||
| body: | | ||
| /test ci/centos/k8s-e2e-external-storage/1.22 |
There was a problem hiding this comment.
| /test ci/centos/k8s-e2e-external-storage/1.22 | |
| /test all |
Can we instead just use all instead of multiple comments ?
There was a problem hiding this comment.
We dont want to trigger all (some experimental) tests we want to trigger individual tests.
|
/retest all |
running |
|
@Mergifyio refresh |
✅ Pull request refreshed |
based on the discussion on the slack channel. we are adding a github action
to trigger the CI jobs when a
ok-to-testlabel is added on the PR.This action is based on below github action https://github.com/peter-evans/create-or-update-comment
Sample Demo avaiable at Madhu-1/label-commentor-action-testing#4
Signed-off-by: Madhu Rajanna madhupr007@gmail.com