Uploaded image for project: 'Couchbase Python Client Library'
  1. Couchbase Python Client Library
  2. PYCBC-845

Nightlies need to build and test (against mock) on more platforms

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0-beta.3
    • 3.0.0
    • tests
    • None
    • 1
    • SDK13: Coll/Txn/Docs More Chip, SDK15: Ruby/Coll/Docs

    Description

      I initially just created.an integration test pipeline – as the scripted build pipeline was difficult to fix/extend. Now, ideally, we'd build and tests against the mock for many python/platform/architecture combinations first, and then do the integration tests against a much more restricted set. Later, we'd have publishing steps in there as well.

      To get part way there, lets do a few things:

      • consider mimicking the recent work that was done by Brett with purely scripted pipelines, they render nicely in blue ocean (the future ui for Jenkins)
      • add a build and test on many platforms. These can be fixed in code, with the integration set of pythons and server versions as parameters. Check how others are doing it too – best to be similar
      • connect the gerrit trigger to this – and only run the build and test when the trigger is used, reserving the integration tests for nightlies and custom runs.
      • connect the manual trigger to this as well, changing the params as needed to match.
      • perhaps add empty tasks for publishing - and at that point create a ticket for that work. Ideally we'd never release from someone's laptop. There will be issues with this in terms of signing the code, etc... So it should be its own task for later.

       

      Minimum required platforms are: Ubuntu, Centos, Windows and MacOS.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          david.kelly David Kelly added a comment -

          We have nightly tests run from scripted-build-pipeline which fit the bill. There are also integration tests, though those are all run on linux. Ideally we will combine these as part of a rework of the Jenkins stuff and then perhaps we would have a single pipeline that does all of this, using different triggers.

          I'll open a ticket specifically for that, and call this one good, as soon as they are reporting centos8 results.

          david.kelly David Kelly added a comment - We have nightly tests run from scripted-build-pipeline which fit the bill. There are also integration tests, though those are all run on linux. Ideally we will combine these as part of a rework of the Jenkins stuff and then perhaps we would have a single pipeline that does all of this, using different triggers. I'll open a ticket specifically for that, and call this one good, as soon as they are reporting centos8 results.
          david.kelly David Kelly added a comment -

          pipeline now builds on Centos, Ubuntu, Windows and Mac, so this is done.  We will integrate the integration and scripted pipeline into one job that does it all (including publishing) later.

          david.kelly David Kelly added a comment - pipeline now builds on Centos, Ubuntu, Windows and Mac, so this is done.  We will integrate the integration and scripted pipeline into one job that does it all (including publishing) later.

          People

            david.kelly David Kelly
            david.kelly David Kelly
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty