public-offering
/
pad.pub0.org
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
pad.pub0.org/.travis.yml

119 lines
4.9 KiB
YAML
Raw Normal View History

first version of a travis.yml file
2012-10-28 15:40:42 +00:00
language: node_js
ci: trivial reformatting in preparation for next commits. This is just needed to slim up the diffs for the next commits. Non functional changes.
2019-12-21 08:07:11 +00:00
first version of a travis.yml file
2012-10-28 15:40:42 +00:00
node_js:
updated nodejs version for travisci
2018-08-27 08:05:35 +00:00
- "lts/*"
ci: trivial reformatting in preparation for next commits. This is just needed to slim up the diffs for the next commits. Non functional changes.
2019-12-21 08:07:11 +00:00
ci: test the Dockerfile Add a `Test Dockerfile` job to Travis that checks the `docker build` exit code. More useful tests can be added later.
2019-12-01 14:38:47 +00:00
services:
- docker
tests: Disable all Travis Caching (#4063)
2020-05-29 20:42:44 +00:00
cache: false
tests: Resolve Gateway timeout during automated tests by adding delay after minify request * Remove npm cache from Travis, this was causing a world of pain. * Remove the broken line attribute tests. * Do a HTTP get against Etherpad to begin minification. * Wait 10 seconds after minification before running tests.
2020-05-29 11:28:31 +00:00
Libreoffice travis (#4159) * remove cruft.. ugh * housekeeping: close stale issues * testing installing LO first
2020-07-10 15:13:06 +00:00
before_install:
Bugfix / tests: Travis use LibreOffice PPA and fix import /export tests for good. (#4166) Just final bits of test coverage for import/export of LibreOffice. It turns out Travis by default installs an old LO that doesn't support PDF import. To remedy that I use the LO PPA and also strict install the PDF import support. Still to do in a future date is check LO exported contents includes expected strings, for now it just checks output length looks sane.
2020-07-16 09:46:45 +00:00
- sudo add-apt-repository -y ppa:libreoffice/ppa
- sudo apt-get update
Libreoffice travis (#4159) * remove cruft.. ugh * housekeeping: close stale issues * testing installing LO first
2020-07-10 15:13:06 +00:00
- sudo apt-get -y install libreoffice
Bugfix / tests: Travis use LibreOffice PPA and fix import /export tests for good. (#4166) Just final bits of test coverage for import/export of LibreOffice. It turns out Travis by default installs an old LO that doesn't support PDF import. To remedy that I use the LO PPA and also strict install the PDF import support. Still to do in a future date is check LO exported contents includes expected strings, for now it just checks output length looks sane.
2020-07-16 09:46:45 +00:00
- sudo apt-get -y install libreoffice-pdfimport
Libreoffice travis (#4159) * remove cruft.. ugh * housekeeping: close stale issues * testing installing LO first
2020-07-10 15:13:06 +00:00
tests: enable sauce labs tests again
2020-03-22 02:11:14 +00:00
install:
- "bin/installDeps.sh"
- "export GIT_HASH=$(git rev-parse --verify --short HEAD)"
tests: Include some plugins in tests (#4339) This PR introduces testing of plugins from the ether/ organization on Github. Each plugin is added into ``.travis``. Frontend plugins tests are run exclusive to core tests. Backend runs both core and plugins with core. Including frontend core tests with plugin tests caused the session to overrun causing errors.
2020-09-26 18:41:33 +00:00
# Installing some plugins
tests: enable sauce labs tests again
2020-03-22 02:11:14 +00:00
script:
- "tests/frontend/travis/runner.sh"
download and start the sauce connector in travis
2012-10-28 16:48:51 +00:00
env:
global:
Update sauce key
2013-06-06 17:16:04 +00:00
- secure: "WMGxFkOeTTlhWB+ChMucRtIqVmMbwzYdNHuHQjKCcj8HBEPdZLfCuK/kf4rG\nVLcLQiIsyllqzNhBGVHG1nyqWr0/LTm8JRqSCDDVIhpyzp9KpCJQQJG2Uwjk\n6/HIJJh/wbxsEdLNV2crYU/EiVO3A4Bq0YTHUlbhUqG3mSCr5Ec="
- secure: "gejXUAHYscbR6Bodw35XexpToqWkv2ifeECsbeEmjaLkYzXmUUNWJGknKSu7\nEUsSfQV8w+hxApr1Z+jNqk9aX3K1I4btL3cwk2trnNI8XRAvu1c1Iv60eerI\nkE82Rsd5lwUaMEh+/HoL8ztFCZamVndoNgX7HWp5J/NRZZMmh4g="
ci: trivial reformatting in preparation for next commits. This is just needed to slim up the diffs for the next commits. Non functional changes.
2019-12-21 08:07:11 +00:00
ci: move the existing test under a jobs section, so we can add others later In the next commit Pierre will start adding tests for the docker build, and this lays out the structure for doing that. No functional changes. The relevant TravisCI docs that motivates moving under a jobs section is https://docs.travis-ci.com/user/build-matrix/ > There are two ways to specify multiple parallel jobs (what we call the build > matrix) with a single .travis.yml configuration file: > > * combine a language-and-environment dependent set of configuration options to > automatically create a matrix of all possible combinations. This is called > matrix expansion. For example, the following configuration produces a build > matrix that expands to 8 individual (2 * 2 * 2) jobs > [...] > > * specify the exact combination of configurations you want in jobs.include. > For example, if not all of those combinations are interesting, you can > specify just the combinations you want
2019-12-21 09:10:35 +00:00
jobs:
tests: travis config
2020-06-08 11:45:03 +00:00
include:
tests: Travis conditional only run frontend tests if it's not a fork. (#4097)
2020-06-08 12:51:57 +00:00
# we can only frontend tests from the ether/ organization and not from forks.
# To request tests to be run ask a maintainer to fork your repo to ether/
- if: fork = false
tests: Include some plugins in tests (#4339) This PR introduces testing of plugins from the ether/ organization on Github. Each plugin is added into ``.travis``. Frontend plugins tests are run exclusive to core tests. Backend runs both core and plugins with core. Including frontend core tests with plugin tests caused the session to overrun causing errors.
2020-09-26 18:41:33 +00:00
name: "Test the Frontend without Plugins"
tests: using travis conditions to decide if front end tests should be run or not. (#4094)
2020-06-08 11:39:20 +00:00
install:
tests: Fix frontend tests (#4188), ugly work around for "Pad never loaded" (#4200) * remote_runner.js: fix drain call (cf. https://github.com/caolan/async/blob/master/CHANGELOG.md#breaking-changes) * dont wait 30 seconds after remote_runner.js returned * timeout frontend tests after 9.5 minutes to prevent travis from silently stop them * log when not all tests finished * prevent killTimeout to happen after last test * log server messages to console * remote_runner will take some time to setup sl, so this second is not necessary * dont write to global mocha variable * mochas `test end` event is not called when a before/beforeEach-hooks failed, so we should only use pass/fail/pending-hooks for logging. also some cruft removed * pass test in `pending`-event handler * remove some more cruft in tests/frontend/runner.js * frontend tests: clarify why stats.tests and total differ * move killTimeout to pass/fail/pending instead of `test end` to guarantee that it is run * delete killTimeout on test end to prevent misleading log message * unused variable * fix regex * unlikely edge case * ensure `allowed test duration exceeded` message is printed for the last runner * get rid of jquery.iframe.js, currently no support for IE<9 * retry up to 3 times when pad could not be loaded * Call the logging code in stopSauce in a callback for `browser.quit()`. This should fix cases like https://app.saucelabs.com/tests/cb8225375d274cbcbb091309f5466cfd Travis received all the logs and remote_runner.js exits, but there never is a DELETE command for webdriver.
2020-07-28 18:57:33 +00:00
#FIXME
- "sed 's/\"loglevel\": \"INFO\",/\"loglevel\": \"WARN\",/g' settings.json.template > settings.json"
tests: no sauce tunnel on ALL test run Speeds up tests and removes overhead
2020-06-08 16:18:22 +00:00
- "tests/frontend/travis/sauce_tunnel.sh"
tests: using travis conditions to decide if front end tests should be run or not. (#4094)
2020-06-08 11:39:20 +00:00
- "bin/installDeps.sh"
- "export GIT_HASH=$(git rev-parse --verify --short HEAD)"
script:
- "tests/frontend/travis/runner.sh"
tests: Include some plugins in tests (#4339) This PR introduces testing of plugins from the ether/ organization on Github. Each plugin is added into ``.travis``. Frontend plugins tests are run exclusive to core tests. Backend runs both core and plugins with core. Including frontend core tests with plugin tests caused the session to overrun causing errors.
2020-09-26 18:41:33 +00:00
- name: "Run the Backend tests without Plugins"
tests: in Travis, also run the backend tests This change introduces automatic execution of the backend tests in Travis. Implements #2351.
2020-04-03 01:27:05 +00:00
install:
tests: Fix backend testing which were always partially broken due to cache (#4053)
2020-05-29 12:26:34 +00:00
- "bin/installDeps.sh"
tests: in Travis, also run the backend tests This change introduces automatic execution of the backend tests in Travis. Implements #2351.
2020-04-03 01:27:05 +00:00
- "cd src && npm install && cd -"
script:
- "tests/frontend/travis/runnerBackend.sh"
Bugfix / tests: Travis use LibreOffice PPA and fix import /export tests for good. (#4166) Just final bits of test coverage for import/export of LibreOffice. It turns out Travis by default installs an old LO that doesn't support PDF import. To remedy that I use the LO PPA and also strict install the PDF import support. Still to do in a future date is check LO exported contents includes expected strings, for now it just checks output length looks sane.
2020-07-16 09:46:45 +00:00
## Temporarily commented out the Dockerfile tests
# - name: "Test the Dockerfile"
# install:
# - "cd src && npm install && cd -"
# script:
# - "docker build -t etherpad:test ."
# - "docker run -d -p 9001:9001 etherpad:test && sleep 3"
# - "cd src && npm run test-container"
tests: Include some plugins in tests (#4339) This PR introduces testing of plugins from the ether/ organization on Github. Each plugin is added into ``.travis``. Frontend plugins tests are run exclusive to core tests. Backend runs both core and plugins with core. Including frontend core tests with plugin tests caused the session to overrun causing errors.
2020-09-26 18:41:33 +00:00
- name: "Load test Etherpad without Plugins"
tests: load testing into core
2020-05-30 18:17:33 +00:00
install:
- "bin/installDeps.sh"
- "cd src && npm install && cd -"
tests: backend tests tweak
2020-05-30 18:22:24 +00:00
- "npm install -g etherpad-load-test"
tests: load testing into core
2020-05-30 18:17:33 +00:00
script:
- "tests/frontend/travis/runnerLoadTest.sh"
tests: Include some plugins in tests (#4339) This PR introduces testing of plugins from the ether/ organization on Github. Each plugin is added into ``.travis``. Frontend plugins tests are run exclusive to core tests. Backend runs both core and plugins with core. Including frontend core tests with plugin tests caused the session to overrun causing errors.
2020-09-26 18:41:33 +00:00
# we can only frontend tests from the ether/ organization and not from forks.
# To request tests to be run ask a maintainer to fork your repo to ether/
- if: fork = false
name: "Test the Frontend Plugins only"
install:
#FIXME
- "sed 's/\"loglevel\": \"INFO\",/\"loglevel\": \"WARN\",/g' settings.json.template > settings.json"
- "tests/frontend/travis/sauce_tunnel.sh"
- "bin/installDeps.sh"
- "rm tests/frontend/specs/*"
- "npm install ep_hash_auth ep_cursortrace ep_subscript_and_superscript ep_headings2 ep_author_hover ep_align ep_webrtc ep_table_of_contents ep_font_size ep_markdown ep_spellcheck"
- "export GIT_HASH=$(git rev-parse --verify --short HEAD)"
script:
- "tests/frontend/travis/runner.sh"
- name: "Run the Backend tests with Plugins"
install:
- "bin/installDeps.sh"
- "npm install ep_hash_auth ep_cursortrace ep_subscript_and_superscript ep_headings2 ep_author_hover ep_align ep_webrtc ep_table_of_contents ep_font_size ep_markdown ep_spellcheck"
- "cd src && npm install && cd -"
script:
- "tests/frontend/travis/runnerBackend.sh"
## Temporarily commented out the Dockerfile tests
# - name: "Test the Dockerfile"
# install:
# - "cd src && npm install && cd -"
# script:
# - "docker build -t etherpad:test ."
# - "docker run -d -p 9001:9001 etherpad:test && sleep 3"
# - "cd src && npm run test-container"
- name: "Load test Etherpad with Plugins"
install:
- "bin/installDeps.sh"
- "npm install ep_hash_auth ep_cursortrace ep_subscript_and_superscript ep_headings2 ep_comments_page ep_author_hover ep_align ep_webrtc ep_table_of_contents ep_font_size ep_markdown ep_spellcheck"
- "cd src && npm install && cd -"
- "npm install -g etherpad-load-test"
script:
- "tests/frontend/travis/runnerLoadTest.sh"
security: Support proxy with rate limiting and include CI test coverage for nginx rev proxy (#4373) Previously Etherpad would not pass the correct client IP address through and this caused the rate limiter to limit users behind reverse proxies. This change allows Etherpad to use a client IP passed from a reverse proxy. Note to devs: This header can be spoofed and spoofing the header could be used in an attack. To mitigate additional *steps should be taken by Etherpad site admins IE doing rate limiting at proxy.* This only really applies to large scale deployments but it's worth noting.
2020-10-01 09:39:01 +00:00
- name: "Test rate limit"
install:
- "docker network create --subnet=172.23.42.0/16 ep_net"
- "docker build -f Dockerfile -t epl-debian-slim ."
- "docker build -f tests/ratelimit/Dockerfile.nginx -t nginx-latest ."
- "docker build -f tests/ratelimit/Dockerfile.anotherip -t anotherip ."
- "docker run -p 8081:80 --rm --network ep_net --ip 172.23.42.1 -d nginx-latest"
- "docker run --name etherpad-docker -p 9000:9001 --rm --network ep_net --ip 172.23.42.2 -e 'TRUST_PROXY=true' epl-debian-slim &"
- "docker run --rm --network ep_net --ip 172.23.42.3 --name anotherip -dt anotherip"
- "./bin/installDeps.sh"
script:
- "cd tests/ratelimit && bash testlimits.sh"
ci: move the existing test under a jobs section, so we can add others later In the next commit Pierre will start adding tests for the docker build, and this lays out the structure for doing that. No functional changes. The relevant TravisCI docs that motivates moving under a jobs section is https://docs.travis-ci.com/user/build-matrix/ > There are two ways to specify multiple parallel jobs (what we call the build > matrix) with a single .travis.yml configuration file: > > * combine a language-and-environment dependent set of configuration options to > automatically create a matrix of all possible combinations. This is called > matrix expansion. For example, the following configuration produces a build > matrix that expands to 8 individual (2 * 2 * 2) jobs > [...] > > * specify the exact combination of configurations you want in jobs.include. > For example, if not all of those combinations are interesting, you can > specify just the combinations you want
2019-12-21 09:10:35 +00:00
first version of a travis.yml file
2012-10-28 15:40:42 +00:00
notifications:
test also with node.js v0.6 + notify irc about test results
2012-11-03 14:36:59 +00:00
irc:
channels:
Update .travis.yml
2013-04-15 15:33:20 +00:00
- "irc.freenode.org#etherpad-lite-dev"