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

Add .travis.yml (backport of MDL-51458)

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 2.9.5
    • 2.9.3
    • Unit tests
    • MOODLE_29_STABLE
    • MOODLE_29_STABLE
    • Hide
      Setup
      1. Navigate to https://travis-ci.org
      2. Sign in with GitHub
      3. View your profile page
      4. Hit Sync (if necessary - probably not)
      5. Find 'Moodle', and enable it
      6. Click the cog icon next to id
      7. Ensure that 'Build only if .travis.yml is present' is enabled
      Important

      This will test that you are based upon a stable. Some of these tests may fail if your test branches are based off integration if the commits between origin/master and your branch contain either a linting failure, or a phpunit test failure.

      Basic build test
      1. Create a new branch based off this one (or integration), and push it to your personal github
      2. View travis-ci.org and watch
      Testing a phpunit test failure
      1. Find a unit test and insert a deliberate failure (hint, the first test run is 'core_phpunit_advanced_testcase::test_debugging'.)
      2. Commit the change and push to a branch on your github
      3. View travis-ci.org push
        1. Confirm that the failure was detected in the 3 of the runners
      Test a PHP linting issue
      1. Create a new php file and insert a deliberate PHP linting failure
      2. Commit the change and push to a branch on your github
      3. View travis-ci.org push
        1. Confirm that the failure was detected in the 2 CITEST runs, but not in the phpunit runs
      Show
      Setup Navigate to https://travis-ci.org Sign in with GitHub View your profile page Hit Sync (if necessary - probably not) Find 'Moodle', and enable it Click the cog icon next to id Ensure that 'Build only if .travis.yml is present' is enabled Important This will test that you are based upon a stable. Some of these tests may fail if your test branches are based off integration if the commits between origin/master and your branch contain either a linting failure, or a phpunit test failure. Basic build test Create a new branch based off this one (or integration), and push it to your personal github View travis-ci.org and watch Testing a phpunit test failure Find a unit test and insert a deliberate failure (hint, the first test run is 'core_phpunit_advanced_testcase::test_debugging'.) Commit the change and push to a branch on your github View travis-ci.org push Confirm that the failure was detected in the 3 of the runners Test a PHP linting issue Create a new php file and insert a deliberate PHP linting failure Commit the change and push to a branch on your github View travis-ci.org push Confirm that the failure was detected in the 2 CITEST runs, but not in the phpunit runs

      Because it has actually been helping us to pick up issues before integration.

            dobedobedoh Andrew Lyons
            dobedobedoh Andrew Lyons
            Rajesh Taneja Rajesh Taneja
            Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
            David Monllaó David Monllaó
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.