Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Camel K Image Builder as internal implementation detail to speed up Fuse deployments #4143

Closed
heiko-braun opened this issue Nov 23, 2018 · 4 comments
Assignees
Labels
Epic Use by ZenHub, typically also for user stories

Comments

@heiko-braun
Copy link
Collaborator

heiko-braun commented Nov 23, 2018

As a user, I want to be able to use Camel-K to stand up integrations on Openshift, to be able to benefit from the quick turnaround times.

@pure-bot pure-bot bot added the notif/triage The issue needs triage. Applied automatically to all new issues. label Nov 23, 2018
@heiko-braun heiko-braun added the Epic Use by ZenHub, typically also for user stories label Nov 23, 2018
@lburgazzoli lburgazzoli self-assigned this Jan 9, 2019
@heiko-braun heiko-braun added this to the Sprint 40 (1/4) milestone Jan 9, 2019
@KurtStam
Copy link
Contributor

@lburgazzoli can you point me to the code in Camel-K. I'm wondering if we can package this logic for any maven based build, so that we can speed up the Syndesis build even for this release.

@heiko-braun
Copy link
Collaborator Author

@KurtStam I think it doesn't make sense to backport any of this to Syndesis. I think it's safe to assume that Camel-K will replace the current means to standup integrations soon. Outside Syndesis however, more generally looking at Java/Maven builds on Openshift this might be interesting.

@lburgazzoli
Copy link
Collaborator

It would be quite a big task to implement the same logic in syndesis as it is not just the maven build that is affected but also the way we do package the application would need to be completely rewritten.

@heiko-braun heiko-braun removed notif/triage The issue needs triage. Applied automatically to all new issues. labels Feb 25, 2019
@mastepan
Copy link

QE ignore

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Epic Use by ZenHub, typically also for user stories
Projects
None yet
Development

No branches or pull requests

5 participants