tricircle gate not setup properly for zuul v3

Bug #1776922 reported by Boden R on 2018-06-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Best I can tell the tricircle zuul v3 jobs are not setup correctly.

Since tricircle depends on other master branches of stable projects (for example neutron), it needs to define those as required-projects in it's project.yaml definition [1].

If this is not done, then zuul won't know to use the master branches of these dependencies and we can't properly test the tricircle.

In addition:
- I don't see a lower-requiurements.txt in the tricircle project.
- I don't see neutron and other stable dependencies in requirements.txt

For an example, please see the vmware-nsx project as well as it's job definition in projects.yaml [1] that explicitly calls out its master stable dependencies.

As a result of this improper job config, I think it's difficult for us to properly test/land patches like [2].


baisen (song1) on 2018-06-19
Changed in tricircle:
status: New → Confirmed
Boden R (boden) wrote :

As per discussion in can you help me understand how to proceed short term. It's not realistic for these neutron patches to wait much longer.

Boden R (boden) wrote :

One option to proceed short term is just to let the neutron patch land and then follow up quickly with a patch in tricircle to address. This would cause breakage until the follow-up patch lands, but hopefully not much.

Another option maybe to pin the version/commit of neutron you use to effectively back-level your neutron so such new changes aren't even included until you update the back-leveled version. Frankly I'm not sure this is possible with your current build setup, but maybe is.

baisen (song1) wrote :

hi Boden.

sorry for late to reply. I just come back from beijing to attend a meeting.

plase wait for two days, this may need discuss with the ptl in this week meeting

to find a better and short way to fix this in short time. and complete fix it in

the long time.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers