You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Nicola Ferraro (JIRA)" <ji...@apache.org> on 2018/09/11 21:39:00 UTC

[jira] [Resolved] (CAMEL-12793) Camel K: allow buildless direct deploy

     [ https://issues.apache.org/jira/browse/CAMEL-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicola Ferraro resolved CAMEL-12793.
------------------------------------
    Resolution: Invalid

https://github.com/apache/camel-k/issues/31

> Camel K: allow buildless direct deploy
> --------------------------------------
>
>                 Key: CAMEL-12793
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12793
>             Project: Camel
>          Issue Type: Sub-task
>          Components: camel-k
>            Reporter: Nicola Ferraro
>            Priority: Major
>
> The general way of doing builds expects a build phase where a docker image is generated.
> In some cases, when there are no additional dependencies to load respect to "camel-core" (or respect to a "prebuilt context" we will add in the future), there's no need to build a docker image and we can run the integration directly.
> We can mount the source file as configmap and load it directly in the runtime.
> File mounting will also be the preferred strategy when dealing with ".js" files (independently of the build phase).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)