[AI] OSAC-1647: CI runs E2E tests for documentation-only changes in fulfillment-service

[osac-jira-ai-issue-solver]

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.

[openshift-ci-robot]

@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.

Details

In response to this:

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.

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: osac-jira-ai-issue-solver[bot]
Once this PR has been reviewed and has the lgtm label, please assign adriengentil for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[osac-jira-ai-issue-solver]

CI failures addressed in no-changes.

[omer-vishlitzky]

/ok-to-test
/retest

[github-actions]

Labeled ok-to-test. No pending workflow runs found to approve — tests will be authorized on next trigger.

[github-actions]

Removed ok-to-test label due to new commits. An org member must re-approve with /ok-to-test.

[eranco74]

closing in favor of #415 (already merged)