PeerTube/.travis.yml
Brad Johnson 7f5f4152a4 Refactor: Separated "Other Videos" section into a dedicated component/service (#969)
* Separated "Other Videos" section into a dedicated component/service

I'm currently working on some proof-of-concepts for recommendation
providers that could work with PeerTube to provide useful video
suggestions to the user.

As a first step, I want to have great clarity about how PeerTube,
itself, will surface these videos to the user.

With this branch, I'm refactoring the "recommendations" to make it
easier to swap out different recommender implementations quickly.

Stop recommender from including the video that's being watched.

Ensure always 5 recommendations

* Treat recommendations as a stream of values, rather than a single async value.

* Prioritize readability over HTTP response size early-optimization.

* Simplify pipe
2018-08-31 17:19:21 +02:00

56 lines
1.1 KiB
YAML

language: node_js
node_js:
- "8"
git:
depth: 1
addons:
apt:
sources:
- ubuntu-toolchain-r-test
packages:
- g++-4.9
postgresql: "9.4"
cache: yarn
sudo: false
services:
- postgresql
- redis-server
install:
- CC=gcc-4.9 CXX=g++-4.9 yarn install
before_script:
- wget --no-check-certificate "https://download.cpy.re/ffmpeg/ffmpeg-release-4.0.2-64bit-static.tar.xz"
- tar xf ffmpeg-release-4.0.2-64bit-static.tar.xz
- mkdir -p $HOME/bin
- cp ffmpeg-*/{ffmpeg,ffprobe} $HOME/bin
- export PATH=$HOME/bin:$PATH
- psql -c "create user peertube with password 'peertube';" -U postgres
matrix:
include:
- env: TEST_SUITE=misc
- env: TEST_SUITE=api-1
- env: TEST_SUITE=api-2
- env: TEST_SUITE=api-3
- env: TEST_SUITE=cli
- env: TEST_SUITE=lint
- env: TEST_SUITE=jest
script:
- travis_retry npm run travis -- "$TEST_SUITE"
after_failure:
- cat test1/logs/all-logs.log
- cat test2/logs/all-logs.log
- cat test3/logs/all-logs.log
- cat test4/logs/all-logs.log
- cat test5/logs/all-logs.log
- cat test6/logs/all-logs.log