charm repos do not have stable/mitaka branches - and neither have a
special branch role to run trusty jobs on other branches. Thus remove
all trusty jobs for them, they are completely unused.
Change-Id: I1b772a926673de5dfd98678fcdcb64ea10ffe8c1
Python34 jobs are only run on stable/mitaka.
With Mitaka retirement, we can remove the python 34 jobs.
Remove jobs for all projects with exception for deployment projects -
but remove python34 from charm, they do not have stable/mitaka branches
and thus the python34 jobs are never run there.
Update also grafana.
Change-Id: I41ddb568ba287b6507c74a25bd1918cc22d9a43a
In preparation for migration of all charms to default to using
Python 3, enable non-voting checks to start providing feedback
for proposed changes on py3 compatibility.
Change-Id: Id08e26a210702e7b1fd4e06e5f5f313a770f72bf
With upcoming cross-project goals to make testing against Python 3
mandatory for all Python-based deliverables of official projects, it
makes sense to start including the voting gate-{name}-python35
template directly in the python-jobs job-group. While at it, make
sure Python 3.4 jobs only run on branches prior to stable/newton now
that the Trusty to Xenial switch is complete.
Change-Id: I4466a9702f6d5fd5e07121d3899e5692fbe7de34
Create new custom charm templates so that only the used jobs get
defined. This saves around 220 unused jobs getting generated.
Change-Id: I7699e5fd45058426e38bbeaa1b67e5372fb63d0f
This is part of our efforts to migrate from ubuntu-trusty to
ubuntu-xenial.
Change-Id: Ie3cf959434dd587d2b7677e461404ad1e85290b5
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This moves members of the python-jobs group over to using xenial by
default on >= Newton. We continue to run on trusty on older branches.
Change-Id: Idba3883443e53567435c36dcc833b5f3988d8670
Layers declare a 'build' target, not 'charm-build'.
Ensure that the correct tox target is executed.
Change-Id: I5dcb447da5727720b8211c9c1467f9025a6d6d00
Create repositories and perform initial import of a number
of Charm layer modules associated with the OpenStack Charm
set.
Layers will support two tox targets - pep8 (for linting the
layer) and build (for building out the layer with associated
dependencies).
Change-Id: I53ad2cd7f01e77f6123d9ce3a5eed14b5574e752
Monty Taylor