Skip to content

ci - poc to use ddci on-demand for end-to-end test in feature branch #54946

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.

Sign up for GitHub

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

Draft
NielkSalocin wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −0
Draft

ci - poc to use ddci on-demand for end-to-end test in feature branch #54946

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .dynamic-build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
end-to-end:
static_rule: true
template: .dynamic-build/end-to-end.yml
8 changes: 8 additions & 0 deletions .dynamic-build/end-to-end.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
trigger:
stage: .pre
include: .gitlab-ci.yml

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Nest the downstream trigger configuration

GitLab treats the top-level trigger as the job name, so include is currently parsed as an unsupported job keyword and every on-demand invocation fails CI configuration validation before any E2E test starts. Nest include under a second trigger: key, following the working child-pipeline shape in .gitlab/deploy/trigger_distribution.yml:8-12.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Propagate downstream E2E failures

After nesting this as a valid downstream trigger, omitting strategy: depend or strategy: mirror makes the on-demand job succeed as soon as the child pipeline is created, so DDCI can report a green result while the requested E2E suite later fails. Add a waiting strategy to the nested trigger; the repository documents this exact default behavior in .gitlab/test/functional_test/regression_detector.yml:216-220 and uses strategy: depend where the parent must reflect the child result.

Useful? React with 👍 / 👎.

variables:
RUN_E2E_TESTS: "on"
RUN_KMT_TESTS: "off"
RUN_UNIT_TESTS: "off"

Loading