That’s perfectly reasonable. It would be nice if there was a separate one to pass to builds.
Thanks, -Nick From: Ben Parees <[email protected]<mailto:[email protected]>> Date: Monday, January 25, 2016 at 2:59 PM To: Nicholas Baker <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Passing Environment variables to "oc new-app" i believe oc new-app -e only sets the env variables on the deploymentconfigs it creates, not the buildconfig. This is (weakly) implied by the help text: -e, --env=[]: Specify key value pairs of environment variables to set into each container. in that it refers to setting variables on containers, not builds. On Mon, Jan 25, 2016 at 2:25 PM, Nick Baker <[email protected]<mailto:[email protected]>> wrote: Hey All, I’m having trouble passing environment variables to new-app performing an s2i. The following works: s2i build -e "MAVEN_ARGS=install karaf:assembly karaf:archive -DskipTests -e " git://github.com/CodeOnCoffee/camel-hello-world<http://github.com/CodeOnCoffee/camel-hello-world> fabric8/s2i-k araf dhirajsb/camel-hello-world --loglevel=4 But calling oc new-app does not seem to pass through the varaibles: oc new-app --env="MAVEN_ARGS=install karaf:assembly karaf:archive -DskipTests -e" fabric8/s2i-karaf~git://github.com/CodeOnCoffee/camel-hello-world<http://github.com/CodeOnCoffee/camel-hello-world> oc new-app --env=MAVEN_ARGS="install karaf:assembly karaf:archive -DskipTests -e" fabric8/s2i-karaf~git://github.com/CodeOnCoffee/camel-hello-world<http://github.com/CodeOnCoffee/camel-hello-world> Any help appreciated! Nick _______________________________________________ users mailing list [email protected]<mailto:[email protected]> http://lists.openshift.redhat.com/openshiftmm/listinfo/users -- Ben Parees | OpenShift
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
