Sorry, obviously meant to credit Frédéric. > On 31 May 2018, at 8:00 am, Graham Dumpleton <[email protected]> wrote: > > As Brian says, use a custom assemble script that calls the original. > > For a description of customising the S2I build process, check out the free > eBook for OpenShift at: > > https://www.openshift.com/deploying-to-openshift/ > <https://www.openshift.com/deploying-to-openshift/> > > Chapter 9 covers this and more. > > Graham > >> On 31 May 2018, at 12:09 am, Frederic Giloux <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Brian >> >> If you want your script to be executed by new builds it should be named >> assemble. It can then call the original assemble script, that you may have >> renamed, a python programm or any other thing you need. The run script is >> called when the final container is launched not during the build. >> >> Regards, >> >> Frédéric >> >> On Wed, 30 May 2018, 17:51 Brian Keyes, <[email protected] >> <mailto:[email protected]>> wrote: >> I have an python script in my git hub repo >> >> I want to run that script when I run "oc new-build" >> >> Do I simply place the script in the git hub under .s2i/bin/run ? >> >> is there anything else I have to do???? >> >> thanks >> >> _______________________________________________ >> users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> >> _______________________________________________ >> users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
