fish-shell/.travis.yml

language: cpp
compiler:
  - gcc
  - clang
before_install:
  - sudo apt-get update
install:
  - sudo apt-get install --no-install-recommends bc doxygen expect gettext libncurses5-dev
script:
  - autoreconf
  - ./configure
  - make
  - sudo make install
  - make test SHOW_INTERACTIVE_LOG=1
notifications:
  irc:
    channels:
      - "irc.oftc.net#fish"
    template:
      - "%{repository}#%{build_number} (%{commit} on %{branch} by %{author}): %{message} Details at %{build_url}"
    use_notice: true
    skip_join: true
matrix:
  fast_finish: true
.travis.yml: add https://travis-ci.org/ automatic builds 2014-01-13 16:53:26 +08:00			`language: cpp`
			`compiler:`
			`- gcc`
			`- clang`
			`before_install:`
			`- sudo apt-get update`
			`install:`
math requires bc package 2015-01-20 02:51:22 +08:00			`- sudo apt-get install --no-install-recommends bc doxygen expect gettext libncurses5-dev`
.travis.yml: add https://travis-ci.org/ automatic builds 2014-01-13 16:53:26 +08:00			`script:`
			`- autoreconf`
			`- ./configure`
			`- make`
			`- sudo make install`
Dump interactive logs on travis test failure As far as I know we can't access the build artifacts from Travis, so we can't check the interactive logs after a test failure. Add an environment variable that causes the test runner to dump the logs itself, and set that variable for Travis. 2014-09-20 05:50:34 +08:00			`- make test SHOW_INTERACTIVE_LOG=1`
.travis.yml: add https://travis-ci.org/ automatic builds 2014-01-13 16:53:26 +08:00			`notifications:`
			`irc:`
			`channels:`
			`- "irc.oftc.net#fish"`
.travis.yml: reduce verbosity of IRC notifications 2014-02-11 09:47:29 +08:00			`template:`
			`- "%{repository}#%{build_number} (%{commit} on %{branch} by %{author}): %{message} Details at %{build_url}"`
			`use_notice: true`
			`skip_join: true`
Allow fast failure on Travis. 2014-06-12 02:44:41 +08:00			`matrix:`
			`fast_finish: true`