15.06.2016 0:51, Matt Riedemann пишет:
It was pointed out today in IRC that the Virtuozzo CI has been failing
on this change for the libvirt imagebackend refactor:
https://review.openstack.org/#/c/282580/
Diana was having a hard time sorting out the line numbers in the stack
trace though fro
On 2016-06-16 11:57:11 +0300 (+0300), Evgeny Antyshev wrote:
> Jeremy, thank you for pointing this out! It saved me from such a headache!
> BTW, is there any plan to workaround this in puppet-jenkins?
Probably not in puppet-jenkins since there are alternative
workarounds such as declaring the nece
Jeremy, thank you for pointing this out! It saved me from such a headache!
BTW, is there any plan to workaround this in puppet-jenkins?
On 06/15/2016 08:39 PM, Jeremy Stanley wrote:
On 2016-06-15 13:17:54 +0300 (+0300), Evgeny Antyshev wrote:
[...]
This all started yesterday when I updated Virt
On 6/15/2016 5:17 AM, Evgeny Antyshev wrote:
Hello, Matt!
First of all, I want to apologize for the inconvenience.
This all started yesterday when I updated Virtuozzo CI using latest
puppets, Zuul, Jenkins and other stuff.
The update somehow led to Zuul not passing environment variables like
ZUU
On 2016-06-15 13:17:54 +0300 (+0300), Evgeny Antyshev wrote:
[...]
> This all started yesterday when I updated Virtuozzo CI using latest puppets,
> Zuul, Jenkins and other stuff.
> The update somehow led to Zuul not passing environment variables like
> ZUUL_CHANGE, LOG_PATH to Jenkins job.
[...]
V
Hello, Matt!
First of all, I want to apologize for the inconvenience.
This all started yesterday when I updated Virtuozzo CI using latest
puppets, Zuul, Jenkins and other stuff.
The update somehow led to Zuul not passing environment variables like
ZUUL_CHANGE, LOG_PATH to Jenkins job.
Therefore
15.06.2016 0:51, Matt Riedemann пишет:
It was pointed out today in IRC that the Virtuozzo CI has been failing
on this change for the libvirt imagebackend refactor:
https://review.openstack.org/#/c/282580/
Diana was having a hard time sorting out the line numbers in the stack
trace though fro
It was pointed out today in IRC that the Virtuozzo CI has been failing
on this change for the libvirt imagebackend refactor:
https://review.openstack.org/#/c/282580/
Diana was having a hard time sorting out the line numbers in the stack
trace though from the logs, because they didn't exist in