[rdo-list] Having an upstream patch in RDO: when and how?

[Javier Pena]

----- Original Message -----
> On 04/07/2016 15:58, Javier Pena wrote:
> > 
> >> Hi everybody,
> >> while testing RDO master in CI i discovered this bug [1] and posted
> >> upstream the patch to solve it [2].
> >> Since the patch got merged this morning, now I was wondering how to
> >> understand when this will be available in RDO. At the moment my CI jobs
> >> take the repos from [3], so is there a way (or a place) to follow the
> >> path of this modification and have an idea of when this will be
> >> available in RDO?
> >>
> > 
> > Hi Raoul,
> > 
> > I'm glad you asked that question, so we can write down the answer somewhere
> > :). We have 3 main steps:
> 
> Happy to have made something useful.
> 
> > 1- Once your patch is merged, DLRN will catch it and build an updated
> > openstack-tripleo-heat-templates RPM. Using the merge commit id
> > (043d71d5ce6a1d7c3fc3a8da78ac4ea5622bb6b9), you can find it at
> > https://trunk.rdoproject.org/centos7/report.html . Actually, it's built
> > already ->
> > https://trunk.rdoproject.org/centos7/04/3d/043d71d5ce6a1d7c3fc3a8da78ac4ea5622bb6b9_cbd0900e/
> 
> Crystal clear, looking inside all the builds I see that all the repos
> associated with a project (in this case
> openstack-tripleo-heat-templates) have in common the last part after the
> underscore (in this case _cbd0900e).

This is expected, because there are several RPM packages created from a single source GitHub repo. The last part after the underscore is the short git hash for the distgit (a.k.a. repo where the spec file is), in this case https://github.com/rdo-packages/tripleo-heat-templates-distgit/commits/rpm-master.

> What's the criteria with this? Which rules define which modifications
> should be in a repo? And, most of all, how different repos are put
> together to be tested by a promotion pipeline? Are they always tested as
> single?

In DLRN, repos are incrementally updated, something like:

- The repo mentioned above includes the last version of openstack-tripleo-heat-templates (let's assume it is 1.0.1), and the last versions of every other package built before (let's assume we have foo 1.0.0 and bar 1.1.0)
- When the next package is built (let's say foo 1.0.1), its repo will include the latest version of every package (so foo 1.0.1, bar 1.1.0 and t-h-t 1.0.1).

So, every repo created after building the package we're interested in, includes the package version we want (or a later one).

Finally, the promotion pipeline takes the latest consistent repo, which includes the latest version of every package already.

> Hope this questions are clear :)
> 

Absolutely :).

> > 2- The CI promotion pipeline will check if a repository is "consistent",
> > which means there are no failed-to-build packages, and then take the
> > latest consistent repo through a number of tests. You can check the CI
> > pipeline at https://ci.centos.org/view/rdo/view/promotion-pipeline/
> 
> In the promotion pipeline how can one search for the status of his repo?
> 

In the Jenkins promotion pipeline, the first job is named "rdo-promote-get-hash-master", and it finds the hash. For the latest (failed) execution, it was https://ci.centos.org/job/rdo-promote-get-hash-master/461/console, and the value we see assigned as NEW_HASH includes the commit we were trying to promote.

> > 3- After the CI job promotes a repository, it will create an internal
> > symlink in the DLRN system. There is a job that synchronizes this symlink
> > to
> > http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-master-tested
> > every two hours, and then it is distributed through the CentOS CDN.
> 
> That's clear too.
> 
> > Regards,
> > Javier
> 
> Many thanks,
> 
> Raoul
> 
> >> Many thanks,
> >>
> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1351547
> >> [2] https://review.openstack.org/#/c/336072/
> >> [3] /etc/yum.repos.d/delorean.repo
> >> http://buildlogs.centos.org/centos/7/cloud/x86_64/rdo-trunk-{{ release
> >> }}-tested/delorean.repo
> >>
> >> --
> >> Raoul Scarazzini
> >> rasca at redhat.com
> >>
> >> _______________________________________________
> >> rdo-list mailing list
> >> rdo-list at redhat.com
> >> https://www.redhat.com/mailman/listinfo/rdo-list
> >>
> >> To unsubscribe: rdo-list-unsubscribe at redhat.com
> >>
> 
> --
> Raoul Scarazzini
> rasca at redhat.com
> 
> _______________________________________________
> rdo-list mailing list
> rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
> 
> To unsubscribe: rdo-list-unsubscribe at redhat.com
>