travis-ci

Run grunt build command on Travis CI

你。 提交于 2019-12-04 07:45:06
问题 I am using Travis CI to test and build my project and as part of it I want travis to run grunt build i have tried the following but have had no luck. script: "grunt build" script: "./node_modules/grunt build" script: "./node_modules/grunt/grunt build" script: "./node_modules/grunt/grunt.js build" 回答1: Have you made sure to install grunt-cli globally on your Travis node? My Travis CI config looks like: language: node_js node_js: - "0.8" before_install: npm install -g grunt-cli install: npm

What is the current workflow to debug Travis builds locally?

非 Y 不嫁゛ 提交于 2019-12-04 07:42:51
问题 One used to be able to download Vagrant boxes to debug Travis builds (for GitHub projects for instance). Apparently, this is no longer possible, so how do people currently debug complex Travis build chains locally? 回答1: One way to inspect the build (not to debug, sorry) is to send the build logs to another server on failure. Here is an example: after_failure - sudo tar -czf /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz your-application-logs/ - scp /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz

What should a Python project structure look like for Travis CI to find and run tests?

徘徊边缘 提交于 2019-12-04 05:46:04
I currently have a project with the following .travis.yml file: language: python install: "pip install tox" script: "tox" Locally, tox properly executes and runs 35 tests, but on Travis CI, it runs 0 tests . More details: https://travis-ci.org/neverendingqs/pyiterable/builds/78954867 I also tried other ways, including: language: python python: - "2.6" - "2.7" - "3.2" - "3.3" - "3.4" - "3.5.0b3" - "3.5-dev" - "nightly" # also fails with just `nosetest` and no `install` step install: "pip install coverage unittest2" script: "nosetests --with-coverage --cover-package=pyiterable" They also could

How to access output files in Travis?

↘锁芯ラ 提交于 2019-12-04 05:04:53
I'm trying to deploy an Android library on Bintray using Travis-CI. But when I upload my repo... I got this: Ran lint on variant release: 6 issues found Ran lint on variant debug: 6 issues found Wrote HTML report to file:///home/travis/build/leandroBorgesFerreira/MoreCLoseButton/app/build/outputs/lint-results-debug.html Wrote XML report to file:///home/travis/build/leandroBorgesFerreira/MoreCLoseButton/app/build/outputs/lint-results-debug.xml :app:lint FAILED Normally I would go to my project out put and read the lint-results-debug.html... But I don't know how to access this file in Travis. So

Add SonarQube coverage via shields.io badge

梦想与她 提交于 2019-12-04 04:10:39
I have com.github.xxxxxx:xxxxxx Maven repository and I want add shields badge but I have a invalid badge: https://img.shields.io/sonar/https/sonarqube.com/com.github.noraui:noraui/tech_debt.svg Sonarqube xxxxxx project page: https://sonarqube.com/dashboard?id=com.github.xxxxxx%3Axxxxxx I find a OK sample from an other sonar server: https://img.shields.io/sonar/http/sonar.qatools.ru/ru.yandex.qatools.allure:allure-core/coverage.svg https://img.shields.io/sonar/http/sonar.qatools.ru/ru.yandex.qatools.allure:allure-core/tech_debt.svg Now, i do not use http://shields.io but directly the https:/

travis cannot build because Error: Cannot find module 'react-test-renderer/shallow'

南楼画角 提交于 2019-12-04 03:33:17
问题 The npm run test works fine locally. However , travis insists that the build is failed and it shows the following log : react-test-renderer is an implicit dependency in order to support react@15.5+. Please add the appropriate version to your devDependencies. See https://github.com/airbnb/enzyme#installation No coverage information was collected, exit without writing coverage information /home/travis/build/abdennour/react-csv/node_modules/enzyme/build/react-compat.js:159 throw e; ^ Error:

Elixir mix auto acknowledge

南楼画角 提交于 2019-12-04 02:56:58
I want to run tests of my Phoenix app on Travis-CI. Log excerpt: $ MIX_ENV=test mix do deps.get, compile, test Could not find hex, which is needed to build dependency :phoenix Shall I install hex? [Yn] When it comes to fetching and installing dependencies, it asks if it should install hex . I was wondering if I can pass a --yes option to mix so that it doesn't ask but just installs? As with any unix command, you could pipe yes into the mix command: yes | MIX_ENV=test mix do deps.get, compile, test You can add this command to your before_install section in .travis.yml mix local.hex --force

Is there a way to access and view html report in Travis CI for maven tests?

懵懂的女人 提交于 2019-12-04 01:47:32
Is there a way to access and view html report in Travis CI for maven testng tests ? At this moment, Travis CI logs is the only way I see how many tests passed/failed/skipped etc. Something like this: Tests run: 34, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 50.427 sec Results : Tests run: 34, Failures: 0, Errors: 0, Skipped: 0 However there are surefire reports generated in this directory: [INFO] Surefire report directory: /home/travis/build/xxxx/yyyy/target/surefire-reports I want to access the surefire-reports/index.html file and view the results. Is this possible,could someone help?

How do I configure Travis-CI to use the correct time zone for a rails app?

蹲街弑〆低调 提交于 2019-12-04 01:30:34
In my application.rb, I have config.time_zone = "Pacific Time (US & Canada)" And this works correctly in development/test, and production servers. However when I push to Travis-CI, it appears to be localized to UTC for example the output of I18n.l Time.now . Is there something different about the Travis-CI ruby/rails environment? The way I accomplish setting the timezone is in the before_script section of the travis.yml They give you root access to the VM running your project, so you can simply set the OS timezone that ruby uses: before_script: - echo 'Canada/Pacific' | sudo tee /etc/timezone

Does Travis ci allow ghc versions larger than 7.8?

核能气质少年 提交于 2019-12-04 01:25:55
I just created a Haskell Travis CI project with this .travis.yml : language: haskell ghc: - 7.8 - 7.10 But Travis interprets the second version as 7.1 : https://travis-ci.org/fhaust/dtw/jobs/57648139 The version is only recognized if I enclose it in quotes (though this results in other errors, since 7.10 is not a version available on Travis CI): language: haskell ghc: - 7.8 - "7.10" Is this a bug? Edit 2015-11-22 There is an open issue for GHC 7.10 on travis-ci: https://github.com/travis-ci/travis-ci/issues/3785 It's not a bug, it's a consequence of using YAML files for config: YAML parses 7