Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
FIS 2.0
-
None
Description
Since FIS 1.0 we support Karaf binary builds from a directory "deployments" containing karaf.zip.
Since OCP now supports binary builds directly --from-file, it would be nice to support these as well (that is, having the karaf.zip directly in the root)
(Currently it is only possible to do "oc start-build karaf-bc --from-file=karaf.zip" only if user adds the following env to karaf-bc
strategy:
sourceStrategy:
env:
- name: ARTIFACT_DIR
value: .
Otherwise, the build will fail with
Pulling image "docker-registry.usersys.redhat.com/fabric8/fis-karaf-openshift:2.0" ... Pulling image "docker-registry.usersys.redhat.com/fabric8/fis-karaf-openshift:2.0" ... Receiving source from STDIN as file sti-karaf-2.0.0-SNAPSHOT.zip ================================================================== Starting S2I Karaf Build ..... Copying binary assembly from /tmp/src/deployments to /deployments ... Please specify an existing build directory ARTIFACT_DIR (tried '/tmp/src/deployments' which does not exist) error: build error: non-zero (13) exit code from docker-registry.usersys.redhat.com/fabric8/fis-karaf-openshift:2.0
