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

69 lines
2.3 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:
- sudo apt-get -y install libreoffice
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)"
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
name: "Test the Frontend"
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: 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: 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
- name: "Run the Backend tests"
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"
WIP - Test Coverage: Import & Export include LibreOffice Test Coverage (#4163) Runs on Travis Will only run locally is ``allowAnyoneToImport`` and ``soffice`` or ``abiword`` is set.
2020-07-14 17:44:53 +00:00
# Set soffice to /usr/bin/soffice
Bugfix: Travis parse (#4164)
2020-07-14 17:47:38 +00:00
- "sed 's/\"soffice\": null,/\"soffice\": \"/usr/bin/soffice\",/g' settings.json.template > settings.json"
WIP - Test Coverage: Import & Export include LibreOffice Test Coverage (#4163) Runs on Travis Will only run locally is ``allowAnyoneToImport`` and ``soffice`` or ``abiword`` is set.
2020-07-14 17:44:53 +00:00
# Set allowAnyoneToImport to true
- "sed 's/\"allowAnyoneToImport\": false,/\"allowAnyoneToInput\": true,/g' settings.json > settings.json"
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"
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
- name: "Test the Dockerfile"
ci: test basic application response of the docker build Note by muxator: This commit introduced a copied & modified version of the testing files loadSettings.js and pad.js. It's Christmas night, and we want to shipt this feature, so I merged it anyway, adding a note in both the original and copied files so that hopefully someone in the distant future is going to merge them back again.
2019-12-03 22:14:00 +00:00
install:
- "cd src && npm install && cd -"
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
script:
ci: test basic application response of the docker build Note by muxator: This commit introduced a copied & modified version of the testing files loadSettings.js and pad.js. It's Christmas night, and we want to shipt this feature, so I merged it anyway, adding a note in both the original and copied files so that hopefully someone in the distant future is going to merge them back again.
2019-12-03 22:14:00 +00:00
- "docker build -t etherpad:test ."
- "docker run -d -p 9001:9001 etherpad:test && sleep 3"
- "cd src && npm run test-container"
tests: load testing into core
2020-05-30 18:17:33 +00:00
- name: "Load test Etherpad"
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: use sed to modify settings for loadTest
2020-05-30 20:02:40 +00:00
# I set loadTest to true
- "sed 's/\"loadTest\": false,/\"loadTest\": true,/g' settings.json.template > settings.json"
tests: load testing into core
2020-05-30 18:17:33 +00:00
script:
- "tests/frontend/travis/runnerLoadTest.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"