We should generate the list of deliverables from the projects.yaml file
in the governance repo. We should also make the submodule entries
relative rather than absolute so that browsing in other places works.
Also, when adding a git submodule, one needs to use the git submodule
add command. So do that, and trim out old no-longer-existing submodules
too.
Change-Id: I97c812f8497cc32a2ee1b418fce2e6bd20af3bc3
Instead of just tracking projects that are part of the integrated gate
lets start tracking all of openstack.
Defining openstack as everything in openstack/ openstack-infra/ and
openstack-dev/
As we move away from a single integrated gate, the list of what should
be in this repo under the old definition is quickly dropping. Instead of
using this to just help debug integrated gate failures, we can use this
to better track all openstack activity.
Knowing the basic nature of a gate failure means you can quickly narrow
down the number of repos that can possibly trigger the failure. That
combined with ElasticSearch data to identify a window of time the issue
was introduced during makes it easy to quickly narrow the number of
patches that could have possibly cause the problems.
Change-Id: I9c04a4d53f4628e0419d744b7e047ad75c0d133d
the openstack/openstack repo is somewhat out of date in the content
that it contains, especially considering all the new oslo modules.
This change creates a script which goes through config repo and
pulls the integrated-gate* projects out. There are a couple of
manual adds after that point, then create the new .gitmodules.
An updated .gitmodules is included.
Change-Id: I5d833a9fd30ca46356cb59b23aac98d0a3e17ed4
Monty Taylor