There is no Jenkins, only Zuul.
Zuul v3 rollout is complete as of 23:00 UTC. At that time, v2 jobs
reported by the "Jenkins" account ceased to be relevant, and v3 jobs
reported by the "Zuul" account are now used to determine whether
your changes can merge.
We have an expedited priority
Thanks. I will try to fix the legacy-trove-functional.
On Sat, Oct 14, 2017 at 12:58 AM, Andreas Jaeger wrote:
> On 2017-10-14 03:30, Sam Matzek wrote:
>> The legacy-trove-functional-dsvm-mysql and
>> legacy-trove-legacy-functional-dsvm-mysql jobs are running the wrong
>>
On 2017-10-14 03:30, Sam Matzek wrote:
> The legacy-trove-functional-dsvm-mysql and
> legacy-trove-legacy-functional-dsvm-mysql jobs are running the wrong
> post_test_hook and have the trove-integration project in $PROJECTS.
Looking at zuul/layout.yaml the change
The legacy-trove-functional-dsvm-mysql and
legacy-trove-legacy-functional-dsvm-mysql jobs are running the wrong
post_test_hook and have the trove-integration project in $PROJECTS.
As such they will always vote -1. The functional integration tests
moved into Trove proper in Ocata. I've added more
The tl;dr is that we're planning to roll forward out of our partial
Zuul v3 rollback starting at 22:00 UTC on Sunday October 15 (this
weekend), so expect some CI downtime and all of the benefits (though
hopefully none of the drawbacks!) you witnessed when we tried the
first time. At that time, v2
On 2017-10-13 07:15:03 -0600 (-0600), Boden Russell wrote:
> How can projects validate zuul v3 jobs in our current state to prepare
> for the transition?
> Some projects don't even have a verified zuul v3 patch [1] and thus
> really have no way to test and work through v3 issues (IIUC).
>
> Is
On 10/10/17 3:40 AM, Andreas Jaeger wrote:
> The common jobs have been fixed whenever bugs got reported. So, if you
> have current failures, tell us.
How can projects validate zuul v3 jobs in our current state to prepare
for the transition?
Some projects don't even have a verified zuul v3 patch
Gary Kotton writes:
> Hi,
> At the moment the neutron, neutron-lib and many of the decomposed projects
> are still failing with the v3. Does this mean that we are broken from the
> 11th?
> For the decomposed projects we have a work around to help address this in the
>
>
> The common jobs have been fixed whenever bugs got reported. So, if you
> have current failures, tell us. Let me readd a quote from Jeremy:
>
> >> In
> >> the meantime, if you've been digging into recent legacy job failures
> >> for your projects you should consider trying to bring them to
Hi,
At the moment the neutron, neutron-lib and many of the decomposed projects are
still failing with the v3. Does this mean that we are broken from the 11th?
For the decomposed projects we have a work around to help address this in the
short term – need to increase timeout and need a flag from
On 2017-10-10 11:01, Sean McGinnis wrote:
> On Mon, Oct 09, 2017 at 11:59:31PM +, Jeremy Stanley wrote:
>> The tl;dr is that we're planning to roll forward out of our partial
>> Zuul v3 rollback starting at 11:00 UTC on Wednesday October 11
>> (a little over 35 hours from now), so expect some
On Mon, Oct 09, 2017 at 11:59:31PM +, Jeremy Stanley wrote:
> The tl;dr is that we're planning to roll forward out of our partial
> Zuul v3 rollback starting at 11:00 UTC on Wednesday October 11
> (a little over 35 hours from now), so expect some CI downtime and
> all of the benefits (though
The tl;dr is that we're planning to roll forward out of our partial
Zuul v3 rollback starting at 11:00 UTC on Wednesday October 11
(a little over 35 hours from now), so expect some CI downtime and
all of the benefits (though hopefully none of the drawbacks!) you
witnessed when we tried the first
13 matches
Mail list logo