Skip to content

[DO NOT MERGE] Add checkout step for che e2e tests#675

Open
dmytro-ndp wants to merge 3 commits intoche-incubator:mainfrom
dmytro-ndp:patch-3
Open

[DO NOT MERGE] Add checkout step for che e2e tests#675
dmytro-ndp wants to merge 3 commits intoche-incubator:mainfrom
dmytro-ndp:patch-3

Conversation

@dmytro-ndp
Copy link
Contributor

@dmytro-ndp dmytro-ndp commented Mar 24, 2026

Add a step to checkout che e2e tests before running smoke tests.

What does this PR do?

Verify if Smoke Test failure for the che-code is a test container image problem, or test code problem.

What issues does this PR fix?

eclipse-che/che#23779

How to test this PR?

Does this PR contain changes that override default upstream Code-OSS behavior?

  • the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
  • the corresponding items were added to the CHANGELOG.md file
  • rules for automatic git rebase were added to the .rebase folder

Summary by CodeRabbit

  • Chores
    • Streamlined PR smoke-test workflow by removing local image build/load steps and related build-time checks.
    • Simplified deployment invocation by dropping an extra operator patch argument.
    • Updated smoke-test asset locations and repository reference for end-to-end tests, and changed e2e artifact upload path.

Added a step to checkout che e2e tests before running smoke tests.
@github-actions
Copy link

github-actions bot commented Mar 24, 2026

Click here to review and test in web IDE: Contribute

@dmytro-ndp dmytro-ndp changed the title Add checkout step for che e2e tests [DO NOT MERGE] Add checkout step for che e2e tests Mar 24, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 24, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 124d313a-1568-4978-82fa-f1d0ca9dbc50

📥 Commits

Reviewing files that changed from the base of the PR and between ff7ceb8 and 7d04667.

📒 Files selected for processing (1)
  • .github/workflows/smoke-test-pr-check.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/smoke-test-pr-check.yaml

📝 Walkthrough

Walkthrough

The GitHub Actions workflow removed local che-code image build/load steps, clones the Eclipse Che repo into ${LOCAL_TEST_DIR}/che for e2e assets, updates volume mounts and artifact paths to che/tests/e2e, and removes the --che-operator-cr-patch-yaml deploy argument and a devfile query param.

Changes

Cohort / File(s) Summary
Workflow update
.github/workflows/smoke-test-pr-check.yaml
Removed steps that build/compile and load che-code Docker images; added cloning of Eclipse Che into ${LOCAL_TEST_DIR}/che; changed e2e container volume mounts from ${LOCAL_TEST_DIR}/tests/e2e/* to ${LOCAL_TEST_DIR}/che/tests/e2e/*; removed --che-operator-cr-patch-yaml deploy arg; removed ?df=smoke-test.devfile.yaml from e2e repo env; changed uploaded artifacts path from /tmp/tests to /tmp/che/tests. Review mounts, env value, and removed image build/load steps.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I hopped and cloned the Chewood tree,
Moved tests to che where they roam free,
No images baked, no tar to load,
Artifacts now take a shorter road,
🥕🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions adding a checkout step for e2e tests, but the actual changes remove Docker artifact steps and restructure test paths, making the title misleading about the primary change. Revise the title to accurately reflect the main changes: removing local Docker builds and restructuring e2e test paths, e.g., 'Remove local Docker builds and restructure e2e test paths in smoke test workflow'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/smoke-test-pr-check.yaml:
- Line 155: The trailing space after the line-continuation backslash in the
docker run volume line "-v ${LOCAL_TEST_DIR}/tests/e2e:/tmp/e2e:Z \ " breaks the
shell continuation; edit that line so the backslash is the final character with
no following space (i.e., change "-v ${LOCAL_TEST_DIR}/tests/e2e:/tmp/e2e:Z \ "
to have the backslash immediately at end of line) to restore proper line
continuation in the workflow.
- Around line 132-134: The checkout step "Checkout che e2e tests" currently
clones into ${LOCAL_TEST_DIR} without pinning a ref and your proposed change
created a path mismatch; fix by pinning the repo using git clone --depth 1
--branch <REF> and clone into ${LOCAL_TEST_DIR}/che (so the cloned code path
matches existing docker volume mounts that expect ${LOCAL_TEST_DIR}/tests/e2e),
OR if you prefer the new layout, update that git clone destination to
${LOCAL_TEST_DIR}/che-e2e-src and also update all docker run volume mounts that
reference ${LOCAL_TEST_DIR}/tests/e2e to point to ${LOCAL_TEST_DIR}/che-e2e-src
(ensure consistency for the ${LOCAL_TEST_DIR} variable and the "Checkout che e2e
tests" step).
- Around line 132-134: The docker run command in the workflow currently uses a
backslash followed by a space to continue the line, which breaks shell
continuation; locate the multi-line "docker run" command in the workflow and
make the backslash the very last character on the continued lines (remove the
trailing space after the backslash) or alternatively join the arguments on one
line or wrap them in quotes so the YAML block preserves intended spacing; ensure
each continuation uses "\" immediately before the newline so the shell sees a
proper line continuation.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 32077e67-edd3-4d07-a92a-419b929ff4e7

📥 Commits

Reviewing files that changed from the base of the PR and between 6671dca and 2fd2fdd.

📒 Files selected for processing (1)
  • .github/workflows/smoke-test-pr-check.yaml

@github-actions
Copy link

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

♻️ Duplicate comments (1)
.github/workflows/smoke-test-pr-check.yaml (1)

29-31: ⚠️ Potential issue | 🟠 Major

Pin the e2e checkout ref for reproducible smoke tests.

The git clone still uses the repository's default branch head without pinning a specific ref. This causes smoke test outcomes to drift over time independent of this PR, making failures non-reproducible.

Consider adding a --branch flag or using a specific commit SHA:

Proposed fix
       - name: Checkout che e2e tests                                                                                                                                                                                                        
         run: |                                                                                                                                                                                                                              
-          git clone --depth 1 https://github.com/eclipse-che/che ${LOCAL_TEST_DIR}/che
+          git clone --depth 1 --branch main https://github.com/eclipse-che/che ${LOCAL_TEST_DIR}/che

For even better reproducibility, consider using a specific tag or commit SHA, or parameterizing the ref via an environment variable.

,

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/smoke-test-pr-check.yaml around lines 29 - 31, Update the
"Checkout che e2e tests" step that runs the git clone so the clone is pinned to
a specific ref: change the git clone invocation used in that step to include a
--branch (or --single-branch) argument pointing to a tag/commit or to an
environment variable (e.g. CHE_REF) so CI uses a stable, reproducible ref
instead of the repo default branch; ensure the step's git clone line references
that env var or explicit SHA/tag and document/validate the variable in the
workflow inputs or env section.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In @.github/workflows/smoke-test-pr-check.yaml:
- Around line 29-31: Update the "Checkout che e2e tests" step that runs the git
clone so the clone is pinned to a specific ref: change the git clone invocation
used in that step to include a --branch (or --single-branch) argument pointing
to a tag/commit or to an environment variable (e.g. CHE_REF) so CI uses a
stable, reproducible ref instead of the repo default branch; ensure the step's
git clone line references that env var or explicit SHA/tag and document/validate
the variable in the workflow inputs or env section.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b1924351-1608-4203-8e32-6fe492c5b35e

📥 Commits

Reviewing files that changed from the base of the PR and between 2fd2fdd and ff7ceb8.

📒 Files selected for processing (1)
  • .github/workflows/smoke-test-pr-check.yaml

@github-actions
Copy link

@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant