You'll need to define the imagestream you've got the build pushing to, the sample does that here: https://github.com/siamaksade/jenkins-s2i-example/blob/master/jenkins-slave-builder-template.yaml#L12-L21
you'll need to name the imagestream "jdk8-jenkins-slave" in your case. On Fri, Aug 5, 2016 at 4:06 PM, Akshaya Khare <[email protected]> wrote: > I've attached the buildconfig, and the project name is "jenkinstin2"... > > On Fri, Aug 5, 2016 at 2:38 PM, Ben Parees <[email protected]> wrote: > >> >> >> On Fri, Aug 5, 2016 at 2:28 PM, Akshaya Khare <[email protected]> >> wrote: >> >>> Hi, >>> >>> I have a project configured in jenkins container(thanks to Ben Parees >>> for suggesting s2i, it works like a charm) running on openshiift which I >>> need to test every time there is a pull request from github. >>> >>> And we are planning to run those test cases on a separate node, since >>> the environment is ideal for testing. >>> I was following this blog by Siamak Sadeghianfar which seems to do >>> exactly the thing which I'm expecting it to do. >>> >>> https://blog.openshift.com/openshift-3-2-jenkins-s2i-slave-pods/ >>> >>> Now whenever I try creating the slave image from the UI, I get an error >>> saying: >>> >>> >>> >>> >>> *"build failed 44 hours ago - 29d91a3: added metadata to Dockerfile >>> (Siamak Sadeghianfar <[email protected] >>> <[email protected]>>)""bc/jenkins is pushing to >>> imagestreamtag/jenkins:latest that is using is/jenkins, but that image >>> stream does not exist"* >>> >> >> can you share your buildconfig definition (json or yaml) and the name of >> the project you've defined it in? >> >> >> >> >>> >>> I can see the docker image :->* <local-ip>:5000/jenkinstin2/jenkins *without >>> any tags. >>> >>> What have I messed up here? >>> >>> And what should be the repository URL for this jenkins-slave-builder, I >>> tried giving my github project url and also the sample >>> jenkins-s2i-example.git url, both end up giving the same error. >>> >> >> the repository the buildconfig references? depends what you want to >> build, but it doesn't sound like that is your current issue. >> >> the example i think you're following uses this repository as the source >> repo input for the slave image build: >> >> https://github.com/siamaksade/jenkins-s2i-example.git >> >> but it uses a context subdirectory of "slave". >> >> you can see the build config definition (and relevant parameters) here: >> https://raw.githubusercontent.com/siamaksade/jenkins-s2i-example/master/jenkins-slave-builder-template.yaml >> >> >> >> >> >>> >>> Also I got the master image running, but apparently the configuration >>> *doesn't* have the one field it certainly needs to have... >>> >>> *Restrict where this project can be run* >>> >> >> sorry, not sure what you're referring to here or where you expect this >> to be configured? >> >> >> >> >>> >>> Is this a bug of some sort? >>> -- >>> *Thanks & Regards,* >>> *AK* >>> *312-785-3508 <312-785-3508>* >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> >> >> -- >> Ben Parees | OpenShift >> >> > > > -- > *Thanks & Regards,* > *Akshaya Khare* > *312-785-3508 <312-785-3508>* > -- Ben Parees | OpenShift
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
