[
https://issues.jboss.org/browse/WFWIP-188?page=com.atlassian.jira.plugin....
]
Michal Jurc commented on WFWIP-188:
-----------------------------------
[~jdenise], [~brian.stansberry]: Do you mean to ask whether including chained builds in
_some_ templates is an acceptable solution?
Well, it is kinda hard to tell for me right now. I would hugely prefer including chained
builds in all templates. Our docs largely mention {{basic-s2i}}, {{tx-recovery-s2i}} and
so on, basically the templates that contain {{JGROUPS_CLUSTER_PASSWORD}}. The quickstarts
refer to these templates as well.
Also, before making an educated guess, I will need to dig in to what it would mean for
disk space usage to have the two images present. I am not sure right now if the two
mentioned images are produced and kept after the build is done and whether both of them
are required for the application to function. If sum of their sizes would be larger than
non-trimmed and both of the images would be required for correct function of the
deployment, that would be kind of bad.
[Galleon] Exisiting EAP templates are not able to use chained builds
--------------------------------------------------------------------
Key: WFWIP-188
URL:
https://issues.jboss.org/browse/WFWIP-188
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Michal Jurc
Assignee: Jean Francois Denise
Priority: Critical
It's not possible to trigger a chained build with existing EAP templates. This kind
of hinders the usability since the existing templates already cover a lot of useful test
cases.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)