Mirrors/thelounge
2
0
Fork 0
mirror of https://github.com/thelounge/thelounge synced 2024-11-27 14:30:57 +00:00
Code Issues Projects Releases Packages Wiki Activity
thelounge/.travis.yml

37 lines
2 KiB
YAML
Raw Normal View History

Add Travis CI configuration file
2016-02-12 04:49:33 +00:00
language: node_js
node_js:
Add Node V9 testing to Travis builds But keep production builds with LTS v8, at least for now.
2017-11-01 06:16:21 +00:00
- 9 # Current stable
- 8 # Active LTS until April 2019
- 6 # Active LTS until April 2018
Add OSX testing to travis, cache node_modules
2016-06-09 09:03:27 +00:00
matrix:
fast_finish: true
Add an extra Travis CI job to make sure production build succeeds and passes tests
2017-01-07 23:53:56 +00:00
include:
Update node versions for travis
2017-05-31 08:49:39 +00:00
- node_js: 8 # Version used to deploy to npm registry
Add an extra Travis CI job to make sure production build succeeds and passes tests
2017-01-07 23:53:56 +00:00
env: BUILD_ENV=production
Add OSX testing to travis, cache node_modules
2016-06-09 09:03:27 +00:00
cache:
directories:
Use CI caches for downloaded files instead of installed ones This allows for a more meaningful build: if a newer version of a sub-package breaks, builds would still pass as it uses the cached version. This uses a cache for downloaded packages instead. I am expecting this to slow down a little bit the builds (but we are OK overall) but be more accurate in practice. See https://docs.npmjs.com/cli/cache#configuration and https://docs.npmjs.com/files/folders#node-modules.
2016-10-12 02:27:57 +00:00
- ~/.npm
Add OSX testing to travis, cache node_modules
2016-06-09 09:03:27 +00:00
Make and document `npm run build` now a mandatory step of the install/build setup This has several reasons, benefits and consequences: - When running on root (which is not recommended anyway), `npm run build` was already necessary. - This allows to not use the `prepublish` hook, whose behavior is going to change in npm v5 and again in npm v6. - This allows to create both production and development builds when running from source. - It makes `npm run build` compatible with Windows again for development environments (lost in previous commit). - It uses the `prepublishOnly` hook added in npm v4. Since this hook is not available prior to that, deployment to npm from Travis has to be done on the Node.js v7 environment.
2017-01-07 23:29:56 +00:00
before_script:
Add an extra Travis CI job to make sure production build succeeds and passes tests
2017-01-07 23:53:56 +00:00
- NODE_ENV=$BUILD_ENV npm run build
Make and document `npm run build` now a mandatory step of the install/build setup This has several reasons, benefits and consequences: - When running on root (which is not recommended anyway), `npm run build` was already necessary. - This allows to not use the `prepublish` hook, whose behavior is going to change in npm v5 and again in npm v6. - This allows to create both production and development builds when running from source. - It makes `npm run build` compatible with Windows again for development environments (lost in previous commit). - It uses the `prepublishOnly` hook added in npm v4. Since this hook is not available prior to that, deployment to npm from Travis has to be done on the Node.js v7 environment.
2017-01-07 23:29:56 +00:00
Don't send an email on a successful build
2016-03-09 08:55:26 +00:00
notifications:
email:
on_success: never
on_failure: always
Add OSX testing to travis, cache node_modules
2016-06-09 09:03:27 +00:00
Add npm deployment step when a Travis CI build passes on a tag
2016-02-12 05:17:55 +00:00
deploy:
Skip cleanup on Travis
2017-09-27 07:39:12 +00:00
skip_cleanup: true # prevent git stash --all which nukes node_modules folder
Add npm deployment step when a Travis CI build passes on a tag
2016-02-12 05:17:55 +00:00
provider: npm
email:
Update secrets in Travis CI, to fix the publication on npm
2016-02-12 07:54:20 +00:00
secure: Eb/dO3VEnuG5CFSJbiTBDZ4X29o1bTITqfzc4SZJqkSKHLZ5/l0VHyd1In7T2U9yBtysnmm+dsOWYFwnH5NMt5kvGkkX754HBDz0QXO//IqADA/1cH1MMXuzJjRvHNrtbq3c6Iv0vO827kXfvqwkfGTmXfreT5w+xF7Y+0SjF8pfu2d/Z5omrmoy9J9SF/kfmahKYZwakc3h8p29JPmnFMUAR0JiZS/2gLSHQnGA3mCcnlO+U3bQuTVW3Z9RhiG51f/EMFfNZ8pBttM6CgE2Zth3AT50jbKjRgYdYN2ee/Z3qUJIoA6dfPALC7B+Z2UekqTiKx4SCk+9vZJJXqT8J+Fe67Dki/FgNWnEZaTn8eFs+Gfh2nnokNZUMd/2mMT0y0KbRaOYQarn6lFw+/Cn9hD6e8uRCqY0+YspMvGtV3LuHFy+br6YphlG6YKxJzExtGDvrwlDD70xJtqcgnlET3XOdzvfCpRSskh7FmVJMoL39f/j9r4FzWVDmfnRnDT6Cac2dSdbQM0Ldw3+65l/57K/Km7NeHbLA3LsnjSJqXuysYwosd6iUOQen59Dy+TvwKafEfAGXWcZNguFURIMf2LRZ4rwTZl6pp30nj23U6rmkWm3JTRZC95i/O4yP2rVoljNUEuMlHVts63r3lwXtuGQVo3+lQCYErK4Ceo7cQc=
Add npm deployment step when a Travis CI build passes on a tag
2016-02-12 05:17:55 +00:00
api_key:
Update secrets in Travis CI, to fix the publication on npm
2016-02-12 07:54:20 +00:00
secure: I9iN31GWI+Mz0xPw81N7qh1M6uidB+3BmiPUXt8QigX45zwp9EhvfZ0U/AIdUyQwzK2RK1zLRQSt+2/1jyeVi+U+AAsRRmaAUx8iqKaQPAkPnQtElolgRP04WSgo7fvNejfM7zS939bQNKG3RlSm04yPgu+ke2igf799p2bpFe2LtyoEeIiUfrUkBiMSpMguN9XF8a7jqCyIouTKjXHR24RmzJ9r7ZoMV27yQauS7XlD81bontzNRZxTytDKdJpZ+sxGIT9mbbtM4LUFX8MeNe3p/bjWavEhrO0ZIpkbOfS/L/w1375YDoNPXxCs288lnGUH+NbGNAEfn+BTz8cmUp7jI7QWR/kNACPeopdAX4OdZxT8wfQcfQZrfCuSpKciOMC7vGgPpQqjQ61t1RKcKs9VUnwC0SwWjyo8LlzkFKnP1ks0eDGYsSoPLdpC9+76UmePkQdxMhscO8TOgkOCcsTMLiyt6ABGOGKu2iE5SsjUYtPiSiRzSBAQENoO560+xBSVTKwqvvhzUAIt4AuAQSgsFjAylDdyzKoObHX12hBdALrqSOOSVwwIQ5/jTgNAsilURHo7KPD407PhRnLOsvumL0qg4sr9S1hjuUKnNla5dg9GY8FVjJ+b2t0A2vgfG1pR1e3vrJRXrpkfRorhmjvKAk2o5you5pQ1Itty7rM=
Add npm deployment step when a Travis CI build passes on a tag
2016-02-12 05:17:55 +00:00
on:
Update node versions for travis
2017-05-31 08:49:39 +00:00
node: 8
Add an extra Travis CI job to make sure production build succeeds and passes tests
2017-01-07 23:53:56 +00:00
condition: "$BUILD_ENV = production"
Add npm deployment step when a Travis CI build passes on a tag
2016-02-12 05:17:55 +00:00
tags: true
repo: thelounge/lounge
Reference in a new issue Copy permalink