mirrors/nextcloud-desktop
1
0
Fork 0
mirror of https://github.com/nextcloud/desktop.git synced 2024-12-21 13:14:30 +03:00
Code Issues Projects Releases Packages Wiki Activity
nextcloud-desktop/.travis.yml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

39 lines
674 B
YAML
Raw Normal View History

Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
os: linux
dist: trusty
Travis coverity: Enforce Ubuntu 14.04 env, fix repo
2016-05-24 12:30:03 +03:00
sudo: required
Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
language: generic
Travis coverity: Enforce Ubuntu 14.04 env, fix repo
2016-05-24 12:30:03 +03:00
services:
Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
- docker
Travis coverity: Enforce Ubuntu 14.04 env, fix repo
2016-05-24 12:30:03 +03:00
Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
env:
matrix:
- BUILD_TYPE=debian
Add travis file for coverity_scan branch All things pushed to the "coverity_scan" branch will now get build by Travis and the resulting binary is pushed to Coverity and analyzed automatically. Since Coverity has a fair usage policy which allows us up to 8 builds per week with a maximum of 2 builds per day we cannot run this automatedly on every push. Which also doesn't make that much sense. Currently this can be used by reating a "coverity_scan" branch and force-pushing the new code to analyze. If all went well the Travis build should pass and Coverity should display the new information (give it some time to process the build though). In Coverity the SHA of the processed build will be used as version number as well as descriptive text. (we can automate this though in the future as well if we want that too) This will fail at the moment on master since Qt4 builds are failing as per https://ci.owncloud.org/job/client-build-matrix-linux/ - probably something that should get fixed. 1.8 branch worked fine though.
2015-06-08 19:51:48 +03:00
before_install:
Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
- admin/linux/travis-build.sh before_install
Add travis file for coverity_scan branch All things pushed to the "coverity_scan" branch will now get build by Travis and the resulting binary is pushed to Coverity and analyzed automatically. Since Coverity has a fair usage policy which allows us up to 8 builds per week with a maximum of 2 builds per day we cannot run this automatedly on every push. Which also doesn't make that much sense. Currently this can be used by reating a "coverity_scan" branch and force-pushing the new code to analyze. If all went well the Travis build should pass and Coverity should display the new information (give it some time to process the build though). In Coverity the SHA of the processed build will be used as version number as well as descriptive text. (we can automate this though in the future as well if we want that too) This will fail at the moment on master since Qt4 builds are failing as per https://ci.owncloud.org/job/client-build-matrix-linux/ - probably something that should get fixed. 1.8 branch worked fine though.
2015-06-08 19:51:48 +03:00
install:
Automatic building of Ubuntu/Debian packages
2017-12-12 19:11:46 +03:00
- admin/linux/travis-build.sh install
before_script:
- admin/linux/travis-build.sh before_script
script:
- admin/linux/travis-build.sh script
after_success:
- admin/linux/travis-build.sh after_success
deploy:
- provider: script
skip_cleanup: true
script: admin/linux/travis-build.sh ppa_deploy
on:
condition: ($BUILD_TYPE = debian)
branches:
except:
- # Do not build tags that we create when we upload to GitHub Releases
- /^(?i:continuous)$/
Reference in a new issue Copy permalink