test: smoke CI run on release_v4.8.1#6
Conversation
Pulls warku123/java-tron-integration-test image and runs --smoke against the FullNode.jar built from the PR. Triggers on PR to develop/release_**. Test reports are extracted from the container and uploaded as artifacts. JAVA_HOME is pinned to JDK 8 inside the container so FullNode runs on the production runtime (a few smoke tests assert java.version starts with "1.8"); JAVA_HOME_17 keeps Gradle on JDK 17 for the test tooling.
The smoke target (~74 cases) is a strict subset of the default `test` target (~hundreds of cases). Smoke gives a 5-min PR signal but misses regressions outside the @tag("smoke") classes. Switch to running the full single-node suite (~12-15 min) so PRs catch more issues. Renames job/container/artifact from 'smoke' to 'integration' to reflect the wider scope. Bumps timeout from 30 to 45 minutes.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/workflows/integration-test.yml">
<violation number="1" location=".github/workflows/integration-test.yml:45">
P2: Avoid using the mutable `latest` Docker tag in CI. Pin the integration test image to an immutable digest so runs are reproducible and not exposed to silent upstream image changes.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| run: ./gradlew clean build -x test --no-daemon | ||
|
|
||
| - name: Pull integration-test image | ||
| run: docker pull warku123/java-tron-integration-test:latest |
There was a problem hiding this comment.
P2: Avoid using the mutable latest Docker tag in CI. Pin the integration test image to an immutable digest so runs are reproducible and not exposed to silent upstream image changes.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/integration-test.yml, line 45:
<comment>Avoid using the mutable `latest` Docker tag in CI. Pin the integration test image to an immutable digest so runs are reproducible and not exposed to silent upstream image changes.</comment>
<file context>
@@ -0,0 +1,78 @@
+ run: ./gradlew clean build -x test --no-daemon
+
+ - name: Pull integration-test image
+ run: docker pull warku123/java-tron-integration-test:latest
+
+ - name: Run integration tests
</file context>
1 participant
Summary
--esevent-plugin boot issue (which manifested on develop/release_v4.8.2 lineage when fix(config): fix the issue where --es fails to start tronprotocol/java-tron#6757 was absent) does not affect release_v4.8.1.Commits
Test plan
Summary by cubic
Adds an Integration Test GitHub Actions workflow for
release_v4.8.1. Runs the full single-node suite to verify CI and confirm the--esevent-plugin boot issue does not affect this release..github/workflows/integration-test.ymltriggered on PRs todevelopandrelease_**.FullNode.jarvia Gradle, runs tests in Dockerwarku123/java-tron-integration-test:latest.--smoke), uploads test artifacts, timeout set to 45 min with concurrency control.Written for commit c48db83. Summary will update on new commits.