Repository navigation
Eclipse: Reproducible build and test workflow on every PR #77
Description
Goal
Give the Eclipse plugin a reproducible automated build and test workflow that
runs on every pull request and push.
Sub-issue of #54.
Acceptance Criteria
- A workflow runs on every pull request and push to
master, and can be run manually. - The workflow compiles the engine headlessly, without an Eclipse installation.
- The workflow runs the shared regression corpus as a required quality gate.
- Engine sources are verified unmodified before compiling, per the SRS constraint.
- A build artifact is retained for review — not practical for Eclipse. The OSGi bundle is built by PDE from the workspace;
pom.xmlis the standalone CLI's POM and contains no Tycho configuration, so there is no headless package step. Tracked in Eclipse: Configure Github Actions CI #16.
Evidence
- CI workflow:
https://github.com/TestSmells/TestSmellDetectorPlugin2026/blob/master/.github/workflows/eclipse-ci.yml - Passing CI run:
https://github.com/TestSmells/TestSmellDetectorPlugin2026/actions/runs/40479663482
b1d5af951d4 - Engine checksums:
https://github.com/TestSmells/TestSmellDetectorPlugin2026/blob/master/tools/corpus/engine-checksums.txt - Corpus runner:
https://github.com/TestSmells/TestSmellDetectorPlugin2026/blob/master/tools/corpus/run-corpus.py - Why there is no headless bundle build:
https://github.com/TestSmells/TestSmellDetectorPlugin2026/blob/master/documentation/architecture-analysis.md
*Link to PR/commit:
TestSmells/TestSmellDetectorPlugin2026_test@0d6d85d394b91210089ef1de4a2da
Activity