Skip to content

32-bit _test_ boxes for Windows #72

Closed

Description

@rvagg

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.

Thoughts? Specifically @kenperkins

Activity

  1. rvagg commented on Apr 13, 2015

    @rvagg
    MemberAuthor
  2. jbergstroem commented on Apr 13, 2015

    @jbergstroem
    Member

    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.

  3. jbergstroem commented on Nov 26, 2015

    @jbergstroem
    Member

    Is this still a thing?

  4. orangemocha commented on Nov 26, 2015

    @orangemocha

    Yes, but I would rather test 32-bit builds on the 64-bit slaves.

  5. maclover7 commented on Feb 10, 2018

    @maclover7
    Contributor

    ping... should this remain open?

  6. maclover7 commented on Feb 18, 2018

    @maclover7
    Contributor

    Closing due to inactivity. Please reopen if this is still needed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions