Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-4508

Define CI operating system coverage rules for the project and (hopefully) simplify CI a little more

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.11.0
    • Fix Version/s: 0.12.0
    • Component/s: Build Process
    • Labels:
      None

      Description

      Currently we build on three linux operating system levels in CI in order to maximize language coverage. We also build against a very old Visual Studio (2010). The project has expended considerable energy attempting to maintain a wide swath of language level coverage stretching back 5 or more years. This has become prohibitively expensive to maintain and must change.

      The proposed new CI operating system coverage rules for the project are:

      Linux

      1. We will run all build jobs on the latest stable Ubuntu operating system, currently Ubuntu Artful (17.10).
      2. Where a linux distribution fails to keep reasonably current with a language we will upgrade it to something more reasonable. (Example: Ubuntu Xenial uses node.js 4.x which is EOL RTS in April 2018, so we install 6.x).
      3. We will additionally run "make check" on the LTS release before the latest stable Ubuntu using all stock provided languages, where supported.

      Windows

      Each build job takes about 20 minutes and there is no parallelization, so we are only going to build 3 jobs:

      1. We will "make check" on the current Visual Studio release, MSVC2017.
      2. We will build one 32-bit cygwin and one 64-bit MinGW job.

      This will yield the following changes:

      1. We will drop the Ubuntu Trusty docker environment and build job.
      2. We will have one "make check" on Ubuntu Xenial (16.04 LTS).
      3. The remainder of jobs will use Ubuntu Artful (17.10), until Bionic (18.04 LTS) comes out.
      4. We will shift from Visual Studio 2010 and 2015 builds to 2017 builds.
      5. We will add a cygwin 32-bit build and keep the 64-bit MinGW build.

      Total build time should be 1 hour or less - we'll see how close we get to that goal.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jking3 James E. King III
                Reporter:
                jking3 James E. King III
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: