Download the PHP package yanniboi/drupal_ti without Composer
On this page you can find all versions of the php package yanniboi/drupal_ti. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download yanniboi/drupal_ti
More information about yanniboi/drupal_ti
Files in yanniboi/drupal_ti
Package drupal_ti
Short Description Drupal - Travis Integration
License GPL-2.0+
Homepage https://github.com/LionsAd/drupal_ti
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package drupal_ti
drupal_ti - Travis Integration for Drupal modules
Versions
Welcome!
Welcome and thanks for trying drupal_ti!
This will make it simple to use travis to test your drupal modules with simpletest and phpunit tests.
All you need is to push your drupal.org repository to Github, setup the module below, login to travis-ci.org, setup the repo and you are up and running in no time.
Setup
Copy .travis.yml.dist to your root folder as .travis.yml and customize the DRUPAL_TI_MODULE_NAME global environment variable to match the name of your module.
You will also need to activate one matrix option, based on if you have support for Simpletest, PHPUnit, Behat or all together:
`
This example would run phpunit as one matrix runner, which gives you results fast, then phpunit, simpletest and behat as the slow runner.
If you want to run drupal_ti with a Drupal-8 module, then you need to use:
`
Using a different tests/ directory.
If your tests/ and composer.json are not in tests/ directory you will want to change:
`
How does it work
drupal_ti provides a drupal-ti command, which is then called with each stage of travis-ci (e.g. install, before_script, ...).
By providing different runners in runners/simpletest or runners/phpunit/ the corresponding scripts are executed (e.g. runners/phpunit/script.sh).
Also diffent environments are included from `, which makes it possible to distinguish easily between Drupal 7 and 8.
This gives you a modular travis experience and such the scripts can be very generic.
Drupal is installed in $TRAVIS_BUILD_DIR/drupal_travis/drupal and drush is available after before_script stage.
How to customize the default behavior
By using
`
you can define your own scripts from your base directory, and drupal_ti will call them before and after your main scripts.
This is useful to change default environment variables, e.g. environments/drupal-7.sh defines
`
but you might want a different version and also override the drupal_ti_install_drupal function (as core-quick-drupal command needs drush 6).
Theoretically you can even define multiple by just seperating them with a space or installed via composer - the possibilities are endless :).
Example:
`
Adding module dependencies from Github repositories
Your module may have several dependencies that are not hosted on Drupal.org. These modules can be added using a custom script and including them in the .travis.yml file.
In .travis.yml you will have a section before_script. The default command here installs drupal and the module we are testing. We can add a command drupal-ti --include [script]. This command will load the script first and then run the default drupal-ti before_script command.
.travis.yml
`
The script path is relative to our /tests directory since we moved to that default directory during the before_install process.
We can now create our custom script as follows,
/tests/drupal_ti/before/before_script.sh
`
The directory /tests/drupal_ti/before/ can also be used to add auto-discovered scripts using a more complex pattern /tests/before/runners/[runner]/[command].sh. This will, however be limited to a specific runner, while the above include pattern will run for all runners.
Script with Composer Manager
Composer manager is a popular dependency and one that requires extra work in order to be set up.
`
Contributions
Contributions are welcome.
Drush
For your convenience the 'drush site-set' command is set for the Drupal installation, so any Drush commands triggered in your own scripts will be run against the test Drupal instance.
