Skip to content

jmix-verify-bootrun: Gate 3 assumes the agent owns the application process #53

Description

@Flaurite

Found while following the skill on a Jmix 3.0.0 project.

Problem: silent — no branch for an app the agent did not start.

Task

Render-walking newly added views against an application the owner had already started on a non-default port.

Where

"Gate 3 — render walk", steps 1, 2 and 4 (start in the background, poll /actuator/health, "Shut the background app down when finished").

What happened

All three steps assume the agent starts the server itself. When the owner has already started it, step 1 does not apply, step 2's readiness poll is redundant, and step 4 is actively wrong — killing that process would terminate something the agent does not own, and "always leave the port free" is the opposite of what is wanted. The port is also assumed to be the default throughout, while the running instance was on another one. Caught at runtime while walking.

Suggested fix

Branch step 1 on whether the app is already running: if it is, take the base URL (including the port) as given, skip the readiness poll, and explicitly do NOT shut it down at the end — leave the process alone and note in the report that the app was not started by the gate. Keep the current start/stop instructions for the case where the agent does own the process.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions