On 2019-12-13 18:01:03 +0100 (+0100), Thierry Carrez wrote:
[...]
> Ideally I would define my own narrow playbook to run the script, without
> inheriting from the standard tox job. However the current script requires
> some dependencies to be installed (openstack-governance, yaml...).
>
> Here are
On Fri, Dec 13, 2019 at 18:01 Thierry Carrez wrote:
[...]
> 3- Abandon the idea of running on the executor -- the trick is that for
> such a short job the overhead of requesting a test node is a bit heavy,
> and we want to run the job on every vote change on release requests
>
> Other ideas?
>
Thierry Carrez writes:
> I moved to implementation on this, but I hit an issue with the
> original plan:
>
>> [...]
>> The job should be lightweight enough to run on the executor. With
>> all those safeguards in place, I do not expect it to trigger
>> significant additional load.
>
> My current i
On Fri, Dec 13, 2019, at 8:48 AM, Saul Wold wrote:
>
> Hello Infra team:
>
> Apparently something got messed up with Launchpad and updating a number
> of starlingx repos with a feature branch.
>
> I was following the methodology of updating a feature branch with
> changes from master via merge
I moved to implementation on this, but I hit an issue with the original
plan:
[...]
The job should be lightweight enough to run on the executor. With all
those safeguards in place, I do not expect it to trigger significant
additional load.
My current implementation is a python script run fr
Hello Infra team:
Apparently something got messed up with Launchpad and updating a number
of starlingx repos with a feature branch.
I was following the methodology of updating a feature branch with
changes from master via merges and I guess when I pushed that to gerrit
and it merged, it cau
