-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Init gradle integration tests #9852
Conversation
It failed on formatting. Otherwise, it looks good to me. Great work @glefloch One thing to be careful about it is dependency caching in our CI. If the pom.xml IT contains no dependencies then if they are not matching those specified in the plugin itself, these dependencies won't be cached in the first step of our CI. |
cb59c50
to
2e9aef1
Compare
@@ -0,0 +1 @@ | |||
version = 999-SNAPSHOT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gsmet here is another version property to keep in mind when releasing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's basically another gradle.properties
file with version
property, in case you have a script for that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for thinking of it :). I'll adjust the release script right away.
containerBuild=true | ||
builderImage="quay.io/quarkus/ubi-quarkus-native-image:19.3.1-java11" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the only way to configure it? Couldn't we propagate the property from the Maven process?
1090eb3
to
b968ce7
Compare
- introduce enums for core extensions - validate duplicate features - deprecate capabilities constants - only extensions that use hard-coded string constants may be broken (due to introduction of naming conventions)
dee6cee
to
c9a76ea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @glefloch!
This branch initializes integration test for the
gradle
module.I moved all
functionalTest
into the integration test module.I also added a specific task for native test. Native test can either be run with gradle using:
or with maven using:
I disable maven compilation for tests as gradle already compiles them. Thus, there is no dependency declaration in
integration-tests/gradle/pom.xml
.I also handle
List
argument type fornativeArgs
property in thequarkusBuild
task as mentionned in #9536.@gastaldi, @aloubyansky could you have a look ?
close #9797
close #9536