Add travis template

[geerteltink]

See #15.

This PR adds a template for Travis CI configuration to attempt to have a central location for templates and communication about possible future changes.

Currently when updating a project the way to have an up-to-date .travis.yml file is looking it up in the latest released package and copy the changes from there. This makes the example config available in a central place.

[weierophinney]

Maybe we should include in that template also variables and commands to deploy documentation.

I'm working on having zfbot build the docs. Since the bot gets triggered for build status events, it can trigger doc builds when it detects a successful build on the master branch. Doing this means we can remove such integration out of the Travis config - which has a nice side effect of preventing token exposure (our previous token was exposed a couple months ago; github revoked it for us when it was detected). It will also make triggering new builds when templates change far easier.

[geerteltink]

I'm working on having zfbot build the docs. Since the bot gets triggered for build status events, it can trigger doc builds when it detects a successful build on the master branch.

Exactly why I didn't include it. And more reason to have a centralized template as others didn't know about this yet.

[froschdesign]

Exactly why I didn't include it.

Exactly why these boilerplates so important, because all others didn't know this!

[geerteltink]

I'm not so happy with these 2 lines:

env:
  global:
    - LEGACY_DEPS="phpunit/phpunit"

install:
  - if [[ $TRAVIS_PHP_VERSION =~ ^5.6 ]]; then travis_retry composer update $COMPOSER_ARGS --with-dependencies $LEGACY_DEPS ; fi

They are not reusable. Can't we write it like this:

matrix:
  include:
    - php: 5.6
      env:
        - DEPS=lowest
        - LEGACY_DEPS="phpunit/phpunit"

install:
  - if [[ $LEGACY_DEPS != "" ]]; then travis_retry composer update $COMPOSER_ARGS --with-dependencies $LEGACY_DEPS ; fi

This way we can reuse it for any php version where needed.

[froschdesign]

@xtreamwayz

This way we can reuse it for any php version where needed.

Makes sense.

[michalbundyra]

I think we will need to set then LEGACY_DEPS only on locked build.

[geerteltink]

• [x] COLUMNS=120 composer show -> only shows package names
• [x] export COLUMNS=120 composer show -> doesn't show anything
• [x] export COLUMNS=120 && composer show -> only shows package names
• [x] stty cols 120 - > works
• [x] stty cols 120 && composer show -> works

For tests and travis composer show output see xtreamwayz/xtreamwayz.com#20

[weierophinney]

Thanks, @xtreamwayz!