On Tue, Dec 5, 2017 at 11:54 AM, Alan Christie <
achris...@informaticsmatters.com> wrote:
> Thanks again, Ben.
>
> I run into two problems with your _alternative_ suggestion … it looked
> really promising because at least you have access to the pod configuration
> (in the Jenkins "Configure System
Thanks again, Ben.
I run into two problems with your _alternative_ suggestion … it looked really
promising because at least you have access to the pod configuration (in the
Jenkins "Configure System->Cloud->Kubernetes”), which is cool, but I encounter
the following in the Jenkins log as it atte
On Tue, Dec 5, 2017 at 10:36 AM, Alan Christie <
achris...@informaticsmatters.com> wrote:
> Thanks Ben. It does seem sensible to use build strategies but prior to a
> wholesale migration to OpenShift, and for existing workflows that may
> contain docker and docker-compose commands is there any rea
Thanks Ben. It does seem sensible to use build strategies but prior to a
wholesale migration to OpenShift, and for existing workflows that may contain
docker and docker-compose commands is there any reasonable option other than a
an external (cloud/proprietary/dedicated) docker-enabled slave? I
On Dec 5, 2017 07:57, "Alan Christie"
wrote:
I’m using Jenkins from the CI/CD catalogue and am able to spin up slaves
and use an `ImageStream` to identify my own slave image. That’s useful, but
what I want to be able to do is build and run Docker images, primarily for
unit/functional test purpose
I’m using Jenkins from the CI/CD catalogue and am able to spin up slaves and
use an `ImageStream` to identify my own slave image. That’s useful, but what I
want to be able to do is build and run Docker images, primarily for
unit/functional test purposes. The _sticking point_, it seems, is the ab
