-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
32-bit _test_ boxes for Windows #72
Comments
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. |
Is this still a thing? |
Yes, but I would rather test 32-bit builds on the 64-bit slaves. |
ping... should this remain open? |
Closing due to inactivity. Please reopen if this is still needed :) |
Currently only doing
x64
builds and test on Windows 2008 and 2012 but we are doing binaries forx86
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.
Thoughts? Specifically @kenperkins
The text was updated successfully, but these errors were encountered: