You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "squakez (via GitHub)" <gi...@apache.org> on 2023/07/03 09:27:54 UTC

[GitHub] [camel-k] squakez commented on pull request #4523: fix(#592): Introduce build order strategy

squakez commented on PR #4523:
URL: https://github.com/apache/camel-k/pull/4523#issuecomment-1617714001

   What I'd like to see as a default is the following behavior:
   
   Given an Integration X with dependencies: a,b
   Given an Integration Y with dependencies: a,b,c
   Given an Integration Z with dependencies: d,e,f
   
   When the Integrations are required to be built at the same time, the operator should be able to start a parallel build for X and Z only so that the Y will be able to reuse the Kit from X. But also we want to have a possible parallelism of Z which has no dependencies in later incremental image reuse.
   
   I think this is what we actually miss.


-- 
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 unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org