[AI] OSAC-1647: CI runs E2E tests for documentation-only changes in fulfillment-service - #360
Conversation
…lment-service Co-authored-by: osac-dev-bot <osac-automation@redhat.com>
|
@osac-jira-ai-issue-solver[bot]: This pull request references OSAC-1647 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: osac-jira-ai-issue-solver[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
CI failures addressed in no-changes. |
2 similar comments
|
CI failures addressed in no-changes. |
|
CI failures addressed in no-changes. |
Co-authored-by: osac-dev-bot <osac-automation@redhat.com>
|
/ok-to-test |
|
Labeled |
|
/retest |
|
Re-triggered failed runs:
|
Co-authored-by: osac-dev-bot <osac-automation@redhat.com>
Co-authored-by: osac-dev-bot <osac-automation@redhat.com>
Resolves OSAC-1647
Summary
CI runs E2E tests for documentation-only changes in fulfillment-service
Description
Description of the problem:
The CI pipeline runs the full end-to-end test suite for all fulfillment-service PRs, including changes that only affect documentation. E2E tests are heavy (they require spinning up a VM, deploying the full stack, etc.), and running them for documentation-only changes wastes CI resources and slows down the review cycle unnecessarily.
Changes limited to the docs/ and examples/ directories in the fulfillment-service repo should not trigger or require the E2E tests to pass.
Affected component: Infrastructure (CI pipeline configuration).
How reproducible:
Always — any PR touching only files in docs/ or examples/ still triggers the full E2E suite.
Steps to reproduce:
Open a PR in the fulfillment-service repo that only modifies files under docs/ or examples/.
Observe that the E2E test jobs are triggered and required to pass.
Expected result:
The CI pipeline should detect that only documentation files changed and skip the E2E test jobs, or mark them as not required for merge.
Actual result:
The full E2E test suite runs and is required to pass, even though the changes cannot affect runtime behavior.