This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
2163 upgrade to camel K 2.1 with windows and mac tests #1670
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
apupier
force-pushed
the
2163-upgradeToCamel2.1WithWindowsAndMactests
branch
8 times, most recently
from
284d376 to
e305ffc
Compare
apupier
force-pushed
the
2163-upgradeToCamel2.1WithWindowsAndMactests
branch
2 times, most recently
from
9c9b0bb to
a0d3d72
Compare
This was referenced Nov 3, 2023
djelinek
reviewed
Nov 6, 2023
basically all tests that do not require a Camel K instance Use spawn using shell to inherit from path context and have access to same binaries than an normal system path on Windows Adapt task definition test for Windows Increase timeout for activation in tests because it is a lot slower on Windows Fix dependency download on Windows Use Maven 3.8.x on CI as it is required by Quarkus version indirectly used by Camel K 1.x Add JBang for CI (which will be required for Camel K 2.x) Use Camel JBang also for the warmup: * it allows to get rid of Maven completely and avoid problems on Windows * requires to apply a workaround inside our codebase due to CAMEL-20033 consisting in replacing backslash by forward slash to the file uri provided Changelog camel-tooling#1591 support for standalone Java files on Windows Double timeout for first integration to be started and visible in Camel K integration view
Signed-off-by: Aurélien Pupier <[email protected]>
- remove command to deploy with a resource as it was provided only for files and this feature has been deprecated in 2.0 and removed in 2.1 - the telemetry indicates that his feature was almost never used anyway see apache/camel-k#4853 (comment) Signed-off-by: Aurélien Pupier <[email protected]>
Signed-off-by: Aurélien Pupier <[email protected]>
apupier
force-pushed
the
2163-upgradeToCamel2.1WithWindowsAndMactests
branch
2 times, most recently
from
a80938a to
960b294
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
djelinek
approved these changes
Nov 7, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mixing both upgrade directly to Camel K 2.1 and providning new tests with Windows and Mac on CI because some parts depends on the others.
Add Windows and Mac platform on CI matrix for a subset of tests, basically all tests that do not require a Camel K instance.
it is fixing Language Support for standalone Java on Windows #1591