It will be useful to expand the options for developing and testing Scheduler code, for example using Github for branching and pull-requests, and Travis Continuous Integration for build testing. This can be done very easily - all we need a .travis.yml file to control the build environment and script.

For more information see https://en.wikipedia.org/wiki/GitHub and https://en.wikipedia.org/wiki/Travis_CI

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jonathan1055 created an issue. See original summary.

jonathan1055’s picture

Status: Active » Needs review
FileSize
13.3 KB

This patch contains:

  • New .travis.yml file, based on the Rules project file, so that Travis builds can be run.
  • New phpcs.xml.dist file to allow the module to tailor specific coding standards sniffs in certain circumstances
  • Modified readme.txt and renamed to README.md to use markdown for better display on Github

To view the project code in Github go to https://github.com/jonathan1055/scheduler
To see the Travis build results go to https://travis-ci.org/jonathan1055/scheduler/branches

  • jonathan1055 committed 1ea7ee3 on 8.x-1.x
    #2916738 Add .travis.yml, README.md and phpcs.xml.dist
    
jonathan1055’s picture

Status: Needs review » Fixed

All seems OK, but I did not expect this to affect testing on d.o. in any case.
Fixed the one extra coding standards message on commit.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

jonathan1055’s picture

Added options into phpcs.xml and removed them from .travis.yml
Don't know why this commit did not create an automatic comment here.

http://cgit.drupalcode.org/scheduler/commit/?id=831e5a3

jonathan1055’s picture

Assigned: jonathan1055 » Unassigned

unassigning