mengw15 opened a new issue, #6276:
URL: https://github.com/apache/texera/issues/6276

   ### Task Summary
   
   #6274 added boot smoke tests for the platform services (in 
`platform-integration`). `texera-web` was left out of scope — it's built in the 
`amber` job (not `platform`), and its boot check belongs in the 
infra-provisioned `amber-integration` job (mirroring how `platform-integration` 
hosts the platform boot checks).
   
   Add a boot smoke test that launches the packaged `texera-web` 
(`bin/texera-web-application`) against `amber-integration`'s infra and asserts 
it reaches a listening state without a runtime classpath/linkage crash — the 
check that would have caught #6204 (Hadoop 3.4 → Jersey `NoClassDefFoundError`) 
before merge.
   
   ### Current state
   
   - `platform-integration` (#6274) boots the 6 platform services strict via 
`.github/scripts/smoke-boot.sh`.
   - `texera-web` boots on **postgres only** (`TexeraWebApplication.run` → 
`SqlServer.initConnection`; no S3 / LakeFS at boot), so `amber-integration`'s 
postgres suffices.
   - `amber-integration` runs `sbt .../test` (no dist); to boot the packaged 
app it needs the amber dist — shipped in via CI artifact from the `amber` job 
(as `platform` does for `platform-integration`), or built there.
   
   ### Suggested direction
   
   - Upload the amber dist as an artifact from the `amber` job.
   - In `amber-integration`, download it and run `smoke-boot.sh 
.../bin/texera-web-application 8080 strict`.
   
   Follow-up to #6220 / #6274; the #6204 Hadoop → Jersey incident is the 
concrete regression it catches.
   
   ### Task Type
   
   - [ ] Refactor / Cleanup
   - [x] DevOps / Deployment / CI
   - [x] Testing / QA
   - [ ] Documentation
   - [ ] Performance
   - [ ] Other
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to