Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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
Comment | File | Size | Author |
---|---|---|---|
#2 | 2916738-2.travis_yml_phpcs_xml.patch | 13.3 KB | jonathan1055 |
|
Comments
Comment #2
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThis patch contains:
.travis.yml
file, based on the Rules project file, so that Travis builds can be run.phpcs.xml.dist
file to allow the module to tailor specific coding standards sniffs in certain circumstancesREADME.md
to use markdown for better display on GithubTo 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
Comment #4
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAll 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.
Comment #6
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded 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
Comment #7
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedunassigning