-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Support "INHERIT" for quarkus.jib.jvm-entrypoint and quarkus.jib.native-entrypoint #28097
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
aaa929d
to
e676c2a
Compare
Interesting! Can you also update one of the integration tests to use this property so we can properly make test it? |
5f27c35
to
6d6af4a
Compare
I added an integration test, |
Did you try the tips mentioned here? Essentially you should use |
…ve-entrypoint jib-maven-plugin and jib-gradle-plugin both support this option to inherit entrypoint from base image, so make Quarkus learn it. Fixed quarkusio#28071
6d6af4a
to
74290e4
Compare
You are right, these properties start the real tests. These tests all passed, I didn't run all tests because it's too slow.
So I think everything should be ok :-) |
Looks good, thanks! |
https://github.com/quarkusio/quarkus/wiki/Release-Planning 2.14 will be released in Nov. , could you cherry-pick this commit into 2.13? This is a very small but useful enhancement for me :-) |
Yeah, I support that would be fine. |
Quarkus 2.13.0 is released, could you backport this to 2.13.1? Thanks! |
That's the point of the label :) |
jib-maven-plugin and jib-gradle-plugin both support this option to inherit entrypoint from base image, so make Quarkus learn it.
Resolves #28071