Skip to content

Commit

Permalink
Enable Downstream trigger job in the architecture repo
Browse files Browse the repository at this point in the history
In order to test VA HCI related changes, we used to run testproject in
the downstream.

downstream-va-hci-trigger-job drops the need of running testproject for
VA HCI related changes.

An developer can trigger the job by adding `trigger github-experimental`
in the pull request comment section. The trigger job will create a
review on
https://review.rdoproject.org/r/q/project:tripleo-downstream-trigger-nested-virt
repo with proper depends-on with the origin pr and dependendent change.

From tripleo-downstream-trigger-nested-virt gerrit review, it will start
VA HCI job downstream in rdo-check pipeline. Once the job finishes, It
will post the results on the gerrit review. Devs can verify the results
before merging it.

Signed-off-by: Chandan Kumar (raukadah) <raukadah@gmail.com>
  • Loading branch information
raukadah committed Aug 23, 2024
1 parent 449b690 commit c122398
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions zuul.d/projects.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,14 @@
- project:
github-experimental-trigger:
jobs:
# This pipeline will be triggered by adding `\trigger github-experimental`
# in the pull request comment.
- downstream-va-hci-trigger-job:
files:
- ^lib
- ^examples/common
- ^examples/dt/hci
- ^va/hci
github-check:
jobs: &id001
- noop
Expand Down

0 comments on commit c122398

Please sign in to comment.