Re: [I] Failing to build native integration [camel-k]

2024-01-12 Thread via GitHub
squakez closed issue #5000: Failing to build native integration URL: https://github.com/apache/camel-k/issues/5000 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscri

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864782870 Yes, as I suspected it's a runtime issue. Try to verify if it is related to groovy DSL or if it's a generic problem, thanks! -- This is an automated message from the Apache Git Ser

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864779355 I ran another test with runtimeVersion set to 3.2.0 and the results were impressive: ``` [1/8] Initializing...

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864768222 Cool, thanks for the info. It gives us the root cause why it's taking actually the double of time. It seems indeed there are the double of classes to scan. Now, I really cannot say i

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864757645 Sure, here it is: ``` [2/8] Performing analysis... [***] (554.8s @ 8.30GB) 43,191 (95.52%) of 45,216 typ

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864697231 BTW, would you mind publishing the entire log trace of the analysis? so we can get some comparison and see how much more classes are scanned. -- This is an automated message from t

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864694794 What I can tell is that since version 2.2.0 we're using Camel 4.2.0 as a default and I recall the groovy dependencies moved to a different project. I don't know if it relates, but su

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864646824 Sorry, I have no idea. We are experiencing the same slowness and I can tell in general it is taking more resources than before. You may engage with Camel Quarkus team or directly wit

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864643342 With a new attempt it ran further and was able to generate the image Here is a summary of the step durations: ``` [1/8] Initializing...

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864607428 You're right. Just found the timeout message in the operator log: `{"level":"info","ts":"2023-12-20T14:44:24Z","logger":"camel-k.controller.build","msg":"Build error","request-na

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864532976 I managed to build it correctly with your same configuration: ``` camel-k-kit-cm1f44plflrc73dahicg-builder quarkus-native [1/8] Initializing...

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864393513 In theory it should as there is quite some memory. I'll try to replicate locally with your same Integration. -- This is an automated message from the Apache Git Service. To respond

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864389850 @squakez I tried tuning the builder by adding the traits: ``` traits: quarkus: buildMode: - native builder: properties: -

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
squakez commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864381370 Yeah, we noticed lately that Quarkus native builds are requiring around 30% of memory more than before. See #4999 - you need to fine tune the builder configuration and provide a set

Re: [I] Failing to build native integration [camel-k]

2023-12-20 Thread via GitHub
lsergio commented on issue #5000: URL: https://github.com/apache/camel-k/issues/5000#issuecomment-1864364848 For comparison purposes, I repeated the process with Camel K 2.1.0 and the build proceeded further, but still failed, as the log shows: ```