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
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 must be doing something wrong. Whenever go guru is fired off against the
origin codebase (for example, with godef or callstack or whicherrs) it
takes several seconds (or more) to do anything, sucking up GB of RAM and
all CPUs. I imagine it must be compiling the world, which is rather large.
Perha
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
In this case I'm also running into
https://github.com/openshift/origin/issues/17588 but perhaps it's all
related.
[origin] $ git describe
v3.9.0-alpha.0-11-ga5c80373e4
[origin] $ go version
go version go1.8.5 linux/amd64
[origin] $ echo $GOPATH
/home/lmeyer/go
[origin] $ time /home/lmeyer/go/bin/g
-- Forwarded message --
From: Luke Meyer
Date: Tue, Dec 5, 2017 at 10:39 AM
Subject: Re: [aos-devel] optimizing go guru
To: Sebastian Jug
Cc: dev
On Tue, Dec 5, 2017 at 9:36 AM, Sebastian Jug wrote:
> Sounds like you have got auto compile still on?
>
>
What does this mean i
In the context of the vim-go plugin. However behavior seems much the same
if I run the same command at the command line (I pulled it out of ps -ef).
On Tue, Dec 5, 2017 at 10:40 AM, Sebastian Jug wrote:
> Are you using guru in some sort of editor/IDE or just standalone?
>
> On Dec 5, 2017 9:40 A
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
Openshift and Kubernetes are massive go projects - over 3 million lines of
code (last I checked). Initial compile can take a few minutes for these
tools. Things to check:
1. Go 1.9 uses less memory when compiling
2. Be sure you are reusing your go compiled artifacts dir between multiple
tools (s
On Tue, Dec 5, 2017 at 10:43 AM, Luke Meyer wrote:
> In the context of the vim-go plugin. However behavior seems much the same
> if I run the same command at the command line (I pulled it out of ps -ef).
>
> On Tue, Dec 5, 2017 at 10:40 AM, Sebastian Jug wrote:
>
>> Are you using guru in some so
On Tue, Dec 5, 2017 at 10:51 AM, Clayton Coleman
wrote:
> Openshift and Kubernetes are massive go projects - over 3 million lines of
> code (last I checked). Initial compile can take a few minutes for these
> tools. Things to check:
>
> 1. Go 1.9 uses less memory when compiling
> 2. Be sure you
If the answer is just "go guru is dog slow, use something else in that
case" then that seems like a useful thing to note in the README :) Along
with what people actually use in development. Seems like a number of tools
rely on guru but everyone complains about how slow it is on large projects.
So t
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 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
On Tue, 2017-11-28 at 13:58 -0500, David Eads wrote:
> As of https://github.com/openshift/origin/pull/17477, h
> ttps://github.com/openshift/api and https://github.com/openshift/client-go are
> the authoritative source of the OpenShift API types and the OpenShift
> external clients. The external t
On Tue, Dec 5, 2017 at 4:13 PM, Simo Sorce wrote:
> On Tue, 2017-11-28 at 13:58 -0500, David Eads wrote:
> > As of https://github.com/openshift/origin/pull/17477, h
> > ttps://github.com/openshift/api and https://github.com/openshift/
> client-go are
> > the authoritative source of the OpenShift
On Tue, 2017-12-05 at 16:25 -0500, Ben Parees wrote:
> On Tue, Dec 5, 2017 at 4:13 PM, Simo Sorce wrote:
>
> > On Tue, 2017-11-28 at 13:58 -0500, David Eads wrote:
> > > As of https://github.com/openshift/origin/pull/17477, h
> > > ttps://github.com/openshift/api and https://github.com/openshift/
17 matches
Mail list logo
