-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set 'mountSources' to 'true' in some example SpringBoot multi-container Devfiles #6761
Set 'mountSources' to 'true' in some example SpringBoot multi-container Devfiles #6761
Conversation
…er Devfiles In those examples, the build and run commands are running in different container components. Without mounting sources in the container used for the 'run' command, this command will not start because Maven would not be able to resolve the 'spring-boot' plugin: ``` ✓ Building your application in container (command: defaultbuild) [39s] • Executing the application (command: defaultrun) ... ✗ Finished executing the application (command: defaultrun) [151ms] ⚠ Devfile command "defaultrun" exited with an error status in 20 second(s) ⚠ Last 100 lines of log: ✗ Waiting for the application to be ready [1m] ⚠ Port forwarding might not work correctly: timeout while checking for ports; ports not listening: (8080 in container "runtime"): context deadline exceeded ⚠ Running `odo logs --follow` might help in identifying the problem. - Forwarding from 127.0.0.1:20001 -> 8080 ``` This was not caught in the tests because failing to run the 'run' command current does not prevent the Dev session from starting. This change might actually make the test faster as we would not have to wait 1 minute to find out that the application port is not reachable.
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
Kudos, SonarCloud Quality Gate passed! |
Flaky E2E test (#6582) /override windows-integration-test/Windows-test |
@rm3l: Overrode contexts on behalf of rm3l: windows-integration-test/Windows-test In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Network issue in E2E tests. /override OpenShift-Integration-tests/OpenShift-Integration-tests |
@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this:
/kind bug
/area testing
What does this PR do / why we need it:
In those examples, the build and run commands are running in
different container components.
Without mounting sources in the container used for the 'run' command,
this command will not start because Maven would not be able
to resolve the 'spring-boot' plugin:
This was not caught in the tests because failing to run the
'run' command currently does not prevent the Dev session from starting.
This change might actually make the test faster as we would not have to wait 1 minute
to find out that the application port is not reachable.
Which issue(s) this PR fixes:
Related to #6754
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: