[openstack-dev] [kolla][infra] does someone cares about Jenkins? I stopped.

Marcin Juszkiewicz marcin.juszkiewicz at linaro.org
Thu Mar 2 09:13:07 UTC 2017

I am working on some improvements for Kolla. Part of that work is
sending patches for review.

Once patch is set for review.openstack.org there is a set of Jenkins
jobs started to make sure that patch does not break already working
code. And this is good thing.

How it is done is not good ;(

1. Kolla output is nightmare to debug.

There is --logs-dir option to provide separate logs for each image build
but it is not used. IMHO it should be as digging through such logs is

Several images feels like they try to do install again and again to pass
through what distribution consider a bug - like "user XY already exists"
bugs while Debian/Ubuntu are used as base distro. Which adds several
error messages to check/ignore.

2. Some jobs fail because "sometimes (not always) the gate can't access
some source on the internet".

I spent most of my career on building software. Having builds fail for
such reasons was hardly acceptable when building could take hours. So we
mirrored all sources and used own mirror(s) as fallback. On other
systems I used 10-20GB w3cache to handle that for me (because there was
no way to provide local mirror of used sources).

OpenStack infrastructure lacks any of it. Using "recheck" comment in
review to restart Jenkins jobs is not a solution - how many times it has
to fail to make sure that it is patch's fault not infrastructure one?

As a contributor I started to ignore Jenkins tests. Instead I do builds
on several machines to check does everything works with my patches. If
something does not then I update my patchset.

More information about the OpenStack-dev mailing list