https://github.com/akai-z/magento2-travis-ci-scripts
Magento 2 Travis CI scripts
https://github.com/akai-z/magento2-travis-ci-scripts
ci code-review continuous continuous-integration integration magento magento-extension magento-module magento2 magento2-extension magento2-module php phpcpd phpcs phpmd testing travis travis-ci unit-testing
Last synced: 5 months ago
JSON representation
Magento 2 Travis CI scripts
- Host: GitHub
- URL: https://github.com/akai-z/magento2-travis-ci-scripts
- Owner: akai-z
- Created: 2017-03-05T22:10:23.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2017-07-09T22:15:08.000Z (almost 9 years ago)
- Last Synced: 2026-01-14T13:27:26.921Z (5 months ago)
- Topics: ci, code-review, continuous, continuous-integration, integration, magento, magento-extension, magento-module, magento2, magento2-extension, magento2-module, php, phpcpd, phpcs, phpmd, testing, travis, travis-ci, unit-testing
- Language: Shell
- Size: 8.79 KB
- Stars: 5
- Watchers: 2
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Magento 2 Travis CI scripts
===========================
The purpose of this package is to provide a simple, clean and time saving way
to create Travis CI configuration file (`.travis.yml`) for Magento 2 modules.
## What is continuous integration (CI)?
Continuous integration is the practice of merging all developer
working copies to a shared mainline several times a day,
in order to prevent integration problems.
([Click here to know more about continuous integration](https://en.wikipedia.org/wiki/Continuous_integration))
## What is Travis CI?
Travis CI is a hosted, distributed continuous integration service
used to build and test software projects hosted at GitHub.
([Click here to know more about Travis CI](https://en.wikipedia.org/wiki/Travis_CI))
([For documentation, click here](https://docs.travis-ci.com/))
## How to use?
* Use the provided configuration distribution file (`.travis.yml.dist`) in this package,
to create your own configuration file.
* In configuration file set your vendor (`VENDOR_NAME`) and module (`MODULE_NAME`) names.
* You could add your own test scripts under `script` step.
* Or, in order to keep things clean and organized, you could put your test scripts inside your module,
and call them with one command from configuration file.
(e.g. `./${MAGENTO_DIR}/${MODULE_DEPLOY_PATH}/dev/travis_ci/script.sh`)
## Covered tests
Tests that are already included in the scripts.
* [PHP_CodeSniffer (PHPCS)](https://github.com/squizlabs/PHP_CodeSniffer).
(Uses [Magento EQP](https://github.com/magento/marketplace-eqp) rules and sniffs)
* [PHP Mess Detector (PHPMD)](https://github.com/phpmd/phpmd).
* [PHP Copy/Paste Detector (PHPCPD)](https://github.com/sebastianbergmann/phpcpd).