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

----- Original Message ----- 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/rp.... 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. Absolutely :). 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.