Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-69267

Better control in .travis.yml about needed services for each job type

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 3.7.8, 3.8.5, 3.9.1, 3.10
    • None
    • General, Unit tests
    • None
    • MOODLE_310_STABLE, MOODLE_37_STABLE, MOODLE_38_STABLE, MOODLE_39_STABLE

    Description

      This is a followup / related with MDL-66322, where we started to use the moodle-exttests docker image to run those tests 100% locally.

      Also, it will impact any other future service in general (containerised or no), say redis, memcached, unoconv, solr...

      The basic idea is that we should launch those services exclusively when the job being run requires them. In this case, it's 99.99% about only starting them when "phpunit" jobs are launched, and keep them out for the rest of jobs (upgrade, grunt, ...).

      But in general, any job should have its organized place to start needed services (say grunt tomorrow requires xxxx that is available via docker... or whatever).

      That's the idea. Ciao

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              stronk7 Eloy Lafuente (stronk7)
              Adrian Greeve, David Woloszyn, Huong Nguyen, Jake Dallimore, Meirza, Michael Hawkins, Raquel Ortega, Safat Shahin, Stevani Andolo
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: