Run script generate-gitmodules.py to sync with governace repository to
add new repositories and remove retired ones.
Change-Id: Ia42b717ad242958ba4a9689ac814c956f460712f
Regenerate .gitmodules after rename.
This also takes into account recent retirement and new creation of repos.
Change-Id: I171261b046cc3f00444ef1f4b2bc0bc646f9b346
Regenerate submodules using the script after the OpenDev change which
moved many projects to another organization.
This removes also some retired repositories and adds newly added ones
since the last run of the script.
Change-Id: Ie8881c7fdd1e86389a8572a06907a6b174f5fef5
The absolute urls here makes allows gerrit to track the submodules, but
it makes doing a submodule update harder, since it makes git try to
clone/fetch directly from gerrit instead of the git farm.
According to the gerrit docs:
https://gerrit-review.googlesource.com/Documentation/user-submodules.html
we can use relative paths. In local testing, the ../.. relative path on
a copy of the repo cloned from git.openstack.org caused a submodule
update to correctly clone from git.openstack.org as well.
Change-Id: I50517d474397c202e7c628b110354832748b6e91
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
zuul gates all of the contained projects in an effective single
timeline. This means that OpenStack, across all of the projects, does
already have a sequence of combinations that have been explcitily
tested, but it's non-trivial to go from a single commit of a particular
project to the commits that were tested with it.
Gerrit's submodule tracking feature will update a super project every
time a subproject is updated, so the specific sequence created by zuul
will be captured by the super project commits.
Andreas Jaeger