21 Sep
2016
21 Sep
'16
6:08 p.m.
On Sep 21 09:23, Karanbir Singh wrote:
Brian,
Is this going to need downtime to fix ? if so, an we get it done in the 10th Oct migration downtime ?
We'll need downtime, but we can probably coordinate this with the 10-October move which will also (barring any last-minute feedback/blockers) coincide with our move to Jenkins 2.
We'll have to continue carrying around a patched version of Jenkins until the fix gets merged into the LTS branch but the bug is marked as a candidate so it shouldn't be long.
-- Brian