Repository navigation
ci: Add Docker image runtime validation - #17
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 783fd5a905
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| --name "$CONTAINER" \ | ||
| -p 127.0.0.1::8081 \ | ||
| -e SERVER_PORT=8081 \ | ||
| -e REDIS_HOST=127.0.0.1 \ |
There was a problem hiding this comment.
127.0.0.1 here is the application container itself, not the runner where the Actions Redis service port is published; GitHub documents that this mapping is accessible from the runner host. Startup unconditionally calls GlobalCapacityBootstrap.run(), whose RedisLeaseCoordinator.registerCapacity() performs a Redis operation, so the container exits with a Redis connection failure and this new validation fails on every hosted-runner CI run. Attach the container to the service network or provide an address that reaches the runner-published Redis port.
Useful? React with 👍 / 👎.
|
Summary
Closes #10
This PR extends the existing GitHub Actions workflow to validate that the built Docker image starts successfully and responds to the application's health endpoint.
Changes
/actuator/healthuntil the application becomes available or the timeout is reached.Validation
The CI workflow will verify that:
No AWS credentials, deployment secrets, or deployment steps are introduced.
Scope
This change adds Docker runtime smoke testing to CI. It does not deploy the application or replace the existing automated test suite.