Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Hi Monty, Thanks for bringing this up. Having run into the topic for a few combination of deps, I'll certainly agree that we need something better than what we currently have. I don't feel that I've enough perspective on the whole system and practices to give a strong opinion on what we

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

On 25/04/2018 18:40, Jeremy Stanley wrote: This came up again a few days ago for sahara-dashboard. We talked through some obvious alternatives to keep its master branch from depending on an unreleased state of horizon and the situation today is that plugin developers have been relying on

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

On 4/25/18 10:13 PM, Shu M. wrote: > Hi folks, > >> unwinding things >> >> >> There are a few different options, but it's important to keep in mind >> that we ultimately want all of the following: >> >> * The code works >> * Tests can run properly in CI >> * "Depends-On" works in

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Monty Taylor wrote on 04/25/2018 09:40:47 AM: ... > Introduce a whitelist of git repo urls, starting with: > >* https://git.openstack.org/openstack/neutron >* https://git.openstack.org/openstack/horizon > We would also need to include at least nova (e.g. [1]) and

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Hi folks, > unwinding things > > > There are a few different options, but it's important to keep in mind > that we ultimately want all of the following: > > * The code works > * Tests can run properly in CI > * "Depends-On" works in CI so that you can test changes cross-repo > *

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Hi team, I'm speaking mostly from Horizon side, but it should be pretty the same for others. We started a discussion today at the Horizon's meeting but we don't have any decision now. For the current release cycle, it looks reasonable to test plugins over the latest master on gates. We're

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

On 2018-04-25 12:03:54 -0400 (-0400), Doug Hellmann wrote: [...] > Especially now with lower-constraints jobs in place, having plugins > rely on features only available in unreleased versions of service > projects doesn't make a lot of sense. We test that way *between* > services using integration

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Excerpts from Monty Taylor's message of 2018-04-25 16:40:47 +0200: > Hi everybody, > > We've been working on navigating through from an interesting situation > over the past few months, but there isn't a top-level overview of what's > going on with it. That's my bad - I've been telling AJaeger

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

On 2018-04-25 16:40:47 +0200 (+0200), Monty Taylor wrote: [...] > * Relax our rules about git repos in test-requirements.txt > > Introduce a whitelist of git repo urls, starting with: > > * https://git.openstack.org/openstack/neutron > * https://git.openstack.org/openstack/horizon > > For