After reading Accelerate, I was interested in figuring out what the lead times were on our deployments.
That is, how long does it take for something to get rolled out after it has been committed to trunk?
We have all the relevant information in compare-revisions, so it seemed straightforward to add it here.
Unfortunately, the change took way longer than I thought, and has at least one bug (see below). I don't think the code is very clear either. Thus, I'm not proposing we merge this. I don't intend to spend further time on this, but am posting the PR in case someone else wants to, and for posterity.
The bug is that we are not matching the upstream code revision to the deploying revision of service-conf correctly, e.g.
After reading Accelerate, I was interested in figuring out what the lead times were on our deployments.
That is, how long does it take for something to get rolled out after it has been committed to trunk?
We have all the relevant information in compare-revisions, so it seemed straightforward to add it here.
Unfortunately, the change took way longer than I thought, and has at least one bug (see below). I don't think the code is very clear either. Thus, I'm not proposing we merge this. I don't intend to spend further time on this, but am posting the PR in case someone else wants to, and for posterity.
The bug is that we are not matching the upstream code revision to the deploying revision of service-conf correctly, e.g.
That deploy did not change the kured version: