You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only doing x64 builds and test on Windows 2008 and 2012 but we are doing binaries for x86 as well.
We have 2 x test boxes for each of 2008 and 2012 currently set up to be redundant so if Jenkins has more work to do then we can overflow and handle more capacity since Windows is one of the slowest to build & test. We could either re-purpose one each of those for 32-bit and lose redundancy or spin up a duplicate set to do 32-bit builds & test.
I say re-purpose. They're not arm-slow and the queue hasn't shown signs of piling up more than two-three jobs.
If/when we run into a resource issue we should find a way of throwing more hardware at it. The real issue here is that we don't test an architecture we treat as primary and release binaries for.
Activity
rvagg commentedon Apr 13, 2015
ref nodejs/node#1389 (comment)
jbergstroem commentedon Apr 13, 2015
I say re-purpose. They're not arm-slow and the queue hasn't shown signs of piling up more than two-three jobs.
If/when we run into a resource issue we should find a way of throwing more hardware at it. The real issue here is that we don't test an architecture we treat as primary and release binaries for.
jbergstroem commentedon Nov 26, 2015
Is this still a thing?
orangemocha commentedon Nov 26, 2015
Yes, but I would rather test 32-bit builds on the 64-bit slaves.
maclover7 commentedon Feb 10, 2018
ping... should this remain open?
maclover7 commentedon Feb 18, 2018
Closing due to inactivity. Please reopen if this is still needed :)