Open Stack

Excerpts from Kiall Mac Innes's message of 2016-08-04 01:27:23 +0100:
> On 18/07/16 20:14, Jeremy Stanley wrote:
> > Note that this will only be true if the change's parent commit in
> > Gerrit was the branch tip at the time it landed. Otherwise (and
> > quite frequently in fact) you will need to identify the SHA of the
> > merge commit which was created at the time it merged and use that
> > instead to find the post job.
> Without wanting to diverge too much from the topic at hand, I believe this
> is why those of us who only occasionally want to look at post job output
> usually just give up! Keeping this in your head for the once every few
> months it's needed is hard ;)
> 
> A change being merged is always (AFAIK) part and parcel with a review
> being closed, so - why not publish to /post/<review-number> (with some
> level of dir sharding)?
> 
> Thanks,
> Kiall
> 

I could never remember the formula for constructing the URL either,
so I built this to help me: https://pypi.python.org/pypi/git-os-job

Doug