feat(studio): ship JavaFX 2 Play and delegate integration tooling
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit

Launch the JavaFX 2 project shell on Java 25 with an interactive viewport,
managed Play lifecycle and project mutation guards. Preserve headless/MCP and
save compatibility, and qualify exact runtime executable bundles.
Separate unit JaCoCo gates from opt-in integration suites and use the internal
Pong fixture for the headless visual pilot.
Move maintenance and native conformance tools into tooling; retain the VS Code
extension and update current navigation links.

Validation: tooling make verify passed, including 1064 Studio unit tests,
JaCoCo thresholds and 22 headless integration tests.
This commit is contained in:
2026-11-19 17:32:03 +00:00
parent 1e17fc4d67
commit 71fb80efc3
163 changed files with 5929 additions and 4950 deletions
+3 -2
View File
@@ -24,6 +24,7 @@ pipeline {
script { env.TESTS_STARTED = 'true' }
withChecks(name: 'Test', includeStage: true) {
withGradle {
// test excludes the integration tag; tooling owns integration execution.
// --continue finishes independent tests/reports but retains a nonzero exit on failure.
sh './gradlew test jacocoTestReport --continue --parallel --max-workers=2 --build-cache --no-daemon --console=plain'
}
@@ -42,8 +43,8 @@ pipeline {
junit testResults: '**/build/test-results/test/TEST-*.xml',
checksName: 'Test / Tests and coverage',
allowEmptyResults: env.VERIFICATION_SUCCEEDED != 'true'
if (env.VERIFICATION_SUCCEEDED == 'true' && !fileExists('prometeu-packer/prometeu-packer-v1/build/test-results/test/TEST-p.packer.services.PackerAssetContractTest.xml')) {
error 'Successful verification is missing the packer contract test report.'
if (env.VERIFICATION_SUCCEEDED == 'true' && !fileExists('prometeu-packer/prometeu-packer-v1/build/test-results/test/TEST-p.packer.services.PackerAssetDeclarationParserTest.xml')) {
error 'Successful verification is missing the packer unit test report.'
}
}
catchError(buildResult: 'FAILURE', stageResult: 'FAILURE') {
+23 -10
View File
@@ -2,16 +2,17 @@
`Jenkinsfile` uses the checked-in Gradle wrapper (currently 9.3.1). A compatible
Java installation must be available to launch Gradle; project conventions select
Java 21 for compilation/tests. The pipeline retains its existing Gradle cache
Java 25 for compilation/tests and the product runtime. Build logic targets Java 21
bytecode independently. The pipeline retains its existing Gradle cache
location, worker limit and installed Jenkins report plugins. It does not require
a named Jenkins Gradle installation.
The build runs on a Unix agent with Java and dependency/cache access. It sets
`JAVA_TOOL_OPTIONS=-Djava.awt.headless=true` for Gradle and test JVMs. No display,
runtime binary, sibling runtime checkout, runtime download/build, or new Jenkins
plugin is required by the packer contract suite.
plugin is required by the unit suite.
## Commands
## Unit pipeline commands
```sh
export JAVA_TOOL_OPTIONS=-Djava.awt.headless=true
@@ -22,8 +23,18 @@ export JAVA_TOOL_OPTIONS=-Djava.awt.headless=true
Clean is a separate stage: when it fails, old reports must not be published as a
new test run. Gradle `--continue` lets independent tasks and reports finish after
a test failure; it does not turn a failing command into success. Runtime/desktop
opt-in test tasks are not invoked. The ordinary packer `test` task includes
`PackerAssetContractTest` without skips or a runtime fallback.
opt-in test tasks are not invoked. All ordinary `test` tasks exclude the JUnit
`integration` tag. Tests involving real process, network, desktop, application
composition or cross-provider pipelines are tagged explicitly, including fixture
subprocesses. This exclusion applies even when optional environment variables are
set. Existing integration suites remain in this repository; `../tooling` prepares
their environment and orchestrates selected integration commands and builds.
No integration suite is executed by the repository pipeline.
The required packer unit report is `PackerAssetDeclarationParserTest`.
`PackerAssetContractTest` is integration-tagged and is not a prerequisite of this
unit-only pipeline. Consolidated coverage consumes only `build/jacoco/test.exec`
from each Java subproject; opt-in integration `.exec` files cannot inflate it.
## Failure reporting
@@ -48,8 +59,9 @@ and any available test results. Artifacts follow the Jenkins job's build/artifac
retention policy.
An otherwise successful verification must produce JUnit results, the packer
contract suite report, consolidated JaCoCo XML and HTML. Missing successful-build
evidence fails publication. A failed compilation may have no reports: the
unit suite report, consolidated JaCoCo XML and HTML. Missing successful-build
evidence fails publication. The required packer report is the unit parser suite.
A failed compilation may have no reports: the
original build failure remains authoritative and available diagnostics are still
preserved. A failed clean does not publish potentially stale artifacts.
@@ -60,9 +72,10 @@ test runs are useful diagnostics, not a passing quality gate.
## Contract and manual verification boundary
See the packer fixture [provenance and coverage](../../prometeu-packer/prometeu-packer-v1/src/test/resources/fixtures/contracts/README.md).
The automated suite checks producer bytes and metadata against independent
expectations. Runtime gameplay remains manual with existing games, not a local
or CI automated test. Record manual outcomes only after execution.
The retained integration contract suite checks producer bytes and metadata against
independent expectations. It is excluded from this unit pipeline. Runtime gameplay
and installed-process verification remain separate integration/desktop checks for
the tooling repository; record their outcomes only after explicit execution.
Local Gradle checks and Groovy parsing cannot certify controller plugin behavior.
A Jenkins run is needed to observe actual report publication and coverage checks;