Hi there,
My proposed fix for Jenkins causing memory leaks in all major browsers has now been accepted upstream. [1] Is there any chance of patching ci.centos.org to include it?
Regards, Laurențiu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/09/16 16:17, Laurentiu Pancescu wrote:
Hi there,
My proposed fix for Jenkins causing memory leaks in all major browsers has now been accepted upstream. [1] Is there any chance of patching ci.centos.org to include it?
Regards, Laurențiu
well done, +1 for finding and then fixing this.
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
Brian,
Is this going to need downtime to fix ? if so, an we get it done in the 10th Oct migration downtime ?
On 19/09/16 16:17, Laurentiu Pancescu wrote:
Hi there,
My proposed fix for Jenkins causing memory leaks in all major browsers has now been accepted upstream. [1] Is there any chance of patching ci.centos.org to include it?
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
On 21/09/16 20:08, Brian Stinson wrote:
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.
Are there still plans to patch the version on ci.centos.org? I still see the original code in hudson-behavior.js - I didn't spend enough time in Jenkins to get into any real trouble, though. :)
Laurențiu
On 13/10/16 09:34, Laurentiu Pancescu wrote:
On 21/09/16 20:08, Brian Stinson wrote:
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.
Are there still plans to patch the version on ci.centos.org? I still see the original code in hudson-behavior.js - I didn't spend enough time in Jenkins to get into any real trouble, though. :)
Laurențiu
Doesnt look like this fix actually went in as yet - Brian can you get it setup for the next maint ?
-
Brian Stinson -
Karanbir Singh -
Karanbir Singh -
Laurentiu Pancescu