Adding OSD and ROSA to the Travis configuration

[pneedle-rh]

This applies to main and enterprise-4.10. #40592 is a separate PR for enterprise-4.9.

This pull request adds the OSD and ROSA collections to the Travis checks. Related PR #40587 was created to test the checks for the two collections.

The PR also updates the build.py script which is called in the .travis.yml file. The addition cleans the drupal-build directory in the Travis VM that is running the checks, rather than just cleaning the distro subdirectory within the drupal-build directory. Without this change, each successive python build.py... command in the travis.yml file will build all of the distros that have been built so far, because the remnants of the previous run continues to exist in the drupal-build directory in the Travis VM.

My understanding is that in main and enterprise-4.10, the build.py script is only called from the .travis.yml file. The sync scripts I think use the build_for_portal.py file instead. Please let me know if the change in this PR might impact other uses for the build.py file that I don't know about. I.e. is there any reason why the previous builds for a different distro might need to remain in the drupal-build directory after the build.py script has run?

We might also need to determine what constitutes a success if multiple distro builds are being run. Would one successful build cause the auto-merge to take place, or would all of the build.py runs need to succeed? How can we test this in Travis?

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: b83f4db

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/61e18e0a86f73a0007eeb473

😎 Browse the preview: https://deploy-preview-40591--osdocs.netlify.app

[ahardin-rh]

@pneedle-rh Great catch and these changes LGTM. I'm personally not sure about the impact on other uses for the build.py file, so I will let others weigh in as well.

[pneedle-rh]

We might also need to determine what constitutes a success if multiple distro builds are being run. Would one successful build cause the automerge to take place, or would all of the build.py runs need to succeed? How can we test this in Travis?

[gaurav-nelson]

@pneedle-rh Maybe we can use a build matrix to run all these test in parallel with multiple jobs? https://docs.travis-ci.com/user/build-matrix/

Build matrixes are currently limited to a maximum of 200 jobs for both private and public repositories. If you are on an open-source plan, please remember that Travis CI provides this service free of charge to the community. So please only specify the matrix you actually need.

EDIT: maybe:

jobs:
  include:
    - name: Build openshift-enterprise
    - language: python
      cache: pip
      sudo: required
      before_install:
      - gem install asciidoctor
      - gem install asciidoctor-diagram

      install:
      - pip3 install pyyaml
      - pip3 install aura.tar.gz

      script:
      - python3 build.py --distro openshift-enterprise --product "OpenShift Container Platform" --version 4.10 --no-upstream-fetch && python3 makeBuild.py

      after_success:
      - bash ./automerge.sh

    - name: Build openshift-dedicated
    - language: python
      cache: pip
      sudo: required
      before_install:
      - gem install asciidoctor
      - gem install asciidoctor-diagram

      install:
      - pip3 install pyyaml
      - pip3 install aura.tar.gz

      script:
      - python3 build.py --distro openshift-dedicated --product "OpenShift Dedicated" --version 4 --no-upstream-fetch && python3 makeBuild.py

    - name: Build openshift-rosa
    - language: python
      cache: pip
      sudo: required
      before_install:
      - gem install asciidoctor
      - gem install asciidoctor-diagram

      install:
      - pip3 install pyyaml
      - pip3 install aura.tar.gz

      script:
      - python3 build.py --distro openshift-rosa --product "Red Hat OpenShift Service on AWS" --version 4 --no-upstream-fetch && python3 makeBuild.py

[gaurav-nelson]

Created travis-ci/docs-travis-ci-com#3153 to check on the build jobs. Also created a support issue with Travis CI.

[pneedle-rh]

@gaurav-nelson thanks for #40741. That is a much better solution that the one I proposed here, so I am closing this PR as obsoleted by your PR. Thanks again!