New to Fabric8, a Question

[websemantics]

Hi Everyone, ..

This might be too obvious, so I apology if so,

What's the take of Fabric8 when it comes to Openshift 3, Source to Image (s2I), .. Does Fabric8 have Custom Builders for creating Docker Images from source or use built in Docker Image builder?

Many thanks,

[rawlingsj]

Hi @websemantics sorry for the delay, I think your question was missed. So we currently use docker onbuild images and custom Builder images in our Jenkinfiles for all non java builds, i.e. node, swift, golang etc and the docker-maven-plugin for java apps.
Having said that we're in the process of moving over to using the openshift binary source builder, so a jenkinsfile or user can create their binaries using the build tools they're used to and pass the aftifacts to openshift to build the image.

This has a number of advantages

• openshift does the heavy lifting of building docker images
• binaries are built in the same way that people are used to, using build tools and scripts native to the language they're developed in and should fit it better with existing CI processes
• from a Jenkinsfile PoV we wont have to run privileged pods or mount the docker socket to perform docker operations - this is a much safer approach

[websemantics]

Thanks @rawlingsj ever so much .. that's great news as greater integration with openshift builders will standardize the practice of source to image for the community .. btw, awesome, awesome work on Fabric8 ..

[rawlingsj]

Yeah we should be switched over to using the openshift binary source soon.

Great to hear you like it :)

[websemantics]

I've downloaded the project source code and trying to make sense of it's large array of components, hopefully understand it well enough to make contributions .. reading the docs currently .. thanks again ..

[rawlingsj]

Sounds great.. we love contributions! If you need any realtime help we hang out on irc.freenode.net #fabric8.