Hi Gerard, What do you want to know exactly ? For packaging, we have this [1] available. For CI there's not much out there right now, that I know of - at least. I'd love to eventually create/improve documentation on: 1) What is delorean, how it works, how to consume it, etc 2) How the CI works, where it's run, how it's involved in testing/packaging/promotion to stable repos, etc The CI is rapidly changing right now, not as fast as I'd like to by Mitaka release I hope we have a solid foundation we can document. Until then, there's little incentive to document it as there are many changes occuring. [1]: https://www.rdoproject.org/packaging/rdo-packaging.html David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Tue, Dec 1, 2015 at 9:51 AM, Gerard Braad <me(a)gbraad.nl&gt; wrote:

2015-12-02 2:52 GMT+01:00 Gerard Braad <me(a)gbraad.nl&gt;: Right here on rdo-list and #rdo IRC meeting every Wed 1500 UTC (agenda at https://etherpad.openstack.org/p/RDO-Packaging ) I'll try tl;dr current RDO build workflow and let David fill-in CI part on top of it: rpm-<release> branches on github/openstack-packages are tracking OpenStack <release> and rpm-master branch is chasing trunk i.e. currently Mitaka-in-development changes. Delorean instance[1] checks every 5min for changes in both upstream source repositories and rpm-* packaging repo and builds RPM packages periodically. CI jobs run with lesser frequency against latest Delorean repository and promote it when it passes both Packstack and RDO-Manager tests. Formal builds are done in CBS Koji instance, provided within CentOS Cloud SIG[2] Until Liberty we had 1:1 mapping for OpenStack/Fedora releases so we were using Fedora branches as distgit, f22=Juno, f23=Kilo. Starting Liberty, we're moving distgit for CBS builds to rdo-liberty branches on github/openstack-packages e.g. [3] where changes from corresponding rpm-* branch are cherry-picked. For build promotion we're not using Bodhi. RDO release managers (currently me and Haikel - number80 on Freenode) manually tag builds in CBS Koji for testing[4] which triggers automated publishing to the testing repo[5] <insert CI against testing repo here> After builds in testing are verified, release managers tag them for release[6], which again triggers nightly signing and publishing procedure to the production repository[7]. Details of sign&push including automatic announcement email are currently under discussion on centos-devel list/IRC channel. Cheers, Alan [1] http://trunk.rdoproject.org/centos7/report.html Delorean code: https://github.com/openstack-packages/delorean instance config: https://github.com/redhat-openstack/delorean-instance [2] https://wiki.centos.org/SpecialInterestGroup/Cloud [3] https://github.com/openstack-packages/aodh/commits/rdo-liberty [4] https://cbs.centos.org/koji/builds?tagID=192 [5] http://buildlogs.centos.org/centos/7/cloud/x86_64/openstack-liberty/ [6] https://cbs.centos.org/koji/builds?tagID=193 [7] http://mirror.centos.org/centos/7/cloud/x86_64/openstack-liberty/

2015-12-29 5:51 GMT+01:00 Gerard Braad <me(a)gbraad.nl&gt;: We have newer builds in testing, they should be promoted during the week, if no issue is reported then. http://buildlogs.centos.org/centos/7/cloud/openstack-liberty/ Regards, H.

2015-12-29 17:28 GMT+01:00 Fox, Kevin M <Kevin.Fox(a)pnnl.gov&gt;: atm, this step is still manual; I'll do the import this week: Regards, H.