Here's a revert of the last change to move forward:
https://review.openstack.org/#/c/252063/
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284
Hi All,
The infra team will be taking gerrit offline for an upgrade on December
16th. We
will start the operation at 17:00 UTC and will continue until about
21:00 UTC.
This outage is to upgrade Gerrit to version 2.11. The IP address of
Gerrit will not be changing.
There is a thread beginning her
cor...@inaugust.com (James E. Blair) writes:
> Once we switch nodepool to use shade, we should consume that
> automatically. In the mean time, I think the best solution for
> current-nodepool is to revert the change to net-name and more-or-less
> mirror the shade behavior change by adding a new c
On Tue, Dec 1, 2015 at 2:27 PM, Mikhail Medvedev wrote:
> Hi Infra team,
>
> Please add and to
> puppet-ciwatch group [1].
Since this is an openstack-infra project I'll need fungi, the infra
PTL, to chime in here.
> The infra-core group should also be added to [1].
The infra-core group should
Hi Infra team,
Please add and to
puppet-ciwatch group [1]. The infra-core group should also be added to [1].
The project was created with [2] and governance change added with [3].
[1] https://review.openstack.org/#/admin/groups/1138,members
[2] https://review.openstack.org/#/c/231699/
[3] htt
Need help with adding Astara to the Activity Board tracking metrics:
Astara Orchestrator - http://git.openstack.org/cgit/openstack/astara
Astara Appliance - http://git.openstack.org/cgit/openstack/astara-appliance
Astara Neutron Plugin - http://git.openstack.org/cgit/openstack/astara-neutron
As
This showed up today after I ran a job to continue to test my 3rd party CI
system. It appears that the $2 argument is not being properly passed to
setup_workspace. The failure shows up when in the scirpt when the argument
is actuall used.
Here's snippets form the relevant log. In the jenkins co
On Tue, Dec 01, 2015 at 04:33:56PM +, Jeremy Stanley wrote:
> On 2015-12-01 09:22:38 +0100 (+0100), Andreas Jaeger wrote:
> > We recently merged changes to limit the running of jobs on
> > project-config to run only when a job is needed.
> >
> > But now we have a change [1] to data/* which is
On 2015-12-01 10:30:09 -0500 (-0500), Paul Belanger wrote:
[...]
> Maybe we need to build out some sort of test coverage for bindep,
> since it exposed missing coverage.
[...]
ITYM test coverage for the jenkins/data/bindep-fallback.txt file. I
was in fact thinking about writing this as recently as
On 2015-12-01 09:22:38 +0100 (+0100), Andreas Jaeger wrote:
> We recently merged changes to limit the running of jobs on
> project-config to run only when a job is needed.
>
> But now we have a change [1] to data/* which is not covered by any
> of the existing jobs and thus no job is run.
>
> Wha
On Tue, Dec 01, 2015 at 09:22:38AM +0100, Andreas Jaeger wrote:
> We recently merged changes to limit the running of jobs on project-config to
> run only when a job is needed.
>
> But now we have a change [1] to data/* which is not covered by any of the
> existing jobs and thus no job is run.
>
>
We recently merged changes to limit the running of jobs on
project-config to run only when a job is needed.
But now we have a change [1] to data/* which is not covered by any of
the existing jobs and thus no job is run.
What shall we do? Always run one of the existing jobs? Extend a job to
c
12 matches
Mail list logo
