Paul Belanger <pabelan...@redhat.com> writes: > Greetings, > > Over the last few weeks I've been helping the RDO project migrate away from > zuulv2 (jenkins) to zuulv3. Today all jobs have been migrated with the help of > the zuul-migrate script. We'll start deleting jenkins bits in the next few > days. > > I wanted to get down some things I've noticed in the process as feedback to > thirdparty CI operators. Hopefully this will help others.
Thanks! > Need for use-cached-repos > ------------------------- > > Today, use-cached-repos is only available to openstack-infra/project-config, > we > should promote this into zuul-jobs to help reduce the amount of pressure on > zuul-executors when jobs start. In the case of 3pci, prepare-workspace role > isn't up to the task to sync everything at once. > > The feedback here, is to some how allow the base job to be smart enough to > work > if a project is found in /opt/git or not. Today we have 2 different images in > rdo, 1 has the cache of upstream git.o.o and other doesn't. I agree. I think we've talked about the possibility of merging the use-cached-repos functionality into prepare-workspace, so that it works in all cases. I think it should be possible and would be a good improvement. > Namespace projects with fqdn > ---------------------------- > > This one is likely unique to rdoproject, but because we have 2 connection to > different gerrit systems, review.rdoproject.org and git.openstack.org, we > actually have duplicate project names. For example: > > openstack/tripleo-common > > which means, for zuul we have to write projects as: > > project: > name: git.openstack.org/openstack/tripleo-common > > project: > name: review.openstack.org/openstack/tripleo-common > > There are legacy reasons for this, and we plan on cleaning review.r.o, however > because of this duplication we cannot use upstream jobs right now. My initial > thought would be to update jobs, in this case devstack to use the following > for > required-projects: > > required-projects: > - git.openstack.org/openstack-dev/devstack > - git.openstack.org/openstack/tripleo-common > > and propose the patch upstream. Again, this is likely specific to rdoproject, > but something right now that blocks them on loading jobs from zuul.o.o. Oh, interesting. I think we may have missed this subtlety when thinking about this use case. I agree that's the best solution for now. > I do have some other suggestions, but they are more specific to zuul. I could > post them here as a follow up or on zuul ML. > > I am happy I was able to help in the original migration of the openstack > projects from jenkins to zuulv3, it did help a lot when I was debugging zuul > failures. But over all rdo project didn't have any major issues with job > content. Thanks for the current (and upcoming) feedback. I think RDO is in a particularly good place to exercise the upstream/downstream sharing of job content; I'm looking forward to more! -Jim _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra