
Both v2 and v3 deployments need to be supported for a bit after zuulv3 feature is merged. The architectures are different, with some parts missing (jenkins), while new parts being added (zuul-exector). It is logical to split the configuration into two using zuulv2 flag. Setting zuulv2 to true would use the old configuration. The choice to use zuulv2 = true instead of zuulv3 = false is made so that it would be easier to remove the flag once v2 support is removed. The support for v3 is not added with this patch. It merely allows for feature/zuulv3 to be merged to master without forcing users of puppet-openstackci to pickup the new version. For zuulv2 using zuul@2.6.0 and nodepool@0.5.0 which represent the latest master state as of this patch. The default used to be 'master' for both in single_node_ci class, so this should minimize unintended consequences for those who used the class with defaults. Change-Id: I2e7cd8d1c8e662b7e21fa80d4fa62846e2d44a70 Story: #2001367 Task: #5951
OpenStack Third-Party CI
These instructions have been moved to doc/source/third_party_ci.rst You can also view the published version here