travis-ci

Rails database setup on Travis-CI

守給你的承諾、 提交于 2019-12-02 16:19:25
I'm trying to use Travis Continuous Integration on a Rails project. The documentation says that the test db must be configured as following for SQLite3: test: adapter: sqlite3 database: ":memory:" timeout: 500 But I'd like to keep my default configuration for local tests. Is it possible to keep both my local settings and the Travis requirements? My solution for this problem is fully based on a blog post with a few differences: Travis CI specific settings in config/database.travis.yml ; cp config/database.travis.yml config/database.yml in before script section of .travis.yml ; I don't have

Showing Travis build status in GitHub repo

 ̄綄美尐妖づ 提交于 2019-12-02 15:42:10
I remember recently seeing the Travis build status of a pr or commit in GitHub browsing the repository (but can't find where). I'm not talking about the Travis build status images in README.md but an actual GitHub feature (green box with a friendly check mark). While my commits build on Travis just fine I'd like to get the results displayed in GitHub (which they don't do right now). I'd like to know how to enable this. UPDATE Found an example here - see the small green check mark saying "Travis-CI build passed"? I give you my example - https://github.com/simkimsia/UtilityBehaviors I wrote this

How to configure Travis-CI to build pull requests & merges to master w/o redundancy

和自甴很熟 提交于 2019-12-02 15:21:51
To put it in "BDD" terms: Background: Given I'm contributing to a GH repo When I create a pull request Then Travis should build the latest commit When I push to an existing pull request Then Travis should build the latest commit When I merge a pull request to master Then Travis should build master I was confused by Travis-CI's "build pushes" and "build PRs" settings, as: Enabling both causes each Pull Request to be build twice by Travis once for the commit on that branch and once again for the merge commit of that branch into its destination Enabling just "build PRs" causes PRs to be built,

Travis CI with Clang 3.4 and C++11

岁酱吖の 提交于 2019-12-02 14:06:46
Is it possible to get Travis CI working with Clang that is capable of C++11? (I want Clang, not GCC, I already have GCC 4.8 working in Travis CI.) It appears that the version that is there pre-installed is not C++11 capable. All my attempts at installing any newer version end up failing because of this : In file included from /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/move.h:57: /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/type_traits:269:39: error: use of undeclared identifier '__float128' struct __is_floating_point_helper<__float128> I have seen the

Sonarcloud failure with Travis, Maven & github [duplicate]

吃可爱长大的小学妹 提交于 2019-12-02 05:15:12
This question already has an answer here: How do I get Sonarcloud to run on pull requests from forks with Travis, Maven & github 3 answers A project I work on ( eclipse/scanning ) uses Travis and Sonar for continuous integration and code analysis. Last week, I noticed that builds were failing at the sonar step with: ERROR: Error during SonarQube Scanner execution org.sonar.squidbridge.api.AnalysisException: Please provide compiled classes of your project with sonar.java.binaries property After some research, I thought I'd fixed this by updating the addons: section ( sonarqube to sonarcloud )

Sonarcloud failure with Travis, Maven & github [duplicate]

谁说我不能喝 提交于 2019-12-02 02:36:15
问题 This question already has answers here : How do I get Sonarcloud to run on pull requests from forks with Travis, Maven & github (3 answers) Closed 2 years ago . A project I work on (eclipse/scanning) uses Travis and Sonar for continuous integration and code analysis. Last week, I noticed that builds were failing at the sonar step with: ERROR: Error during SonarQube Scanner execution org.sonar.squidbridge.api.AnalysisException: Please provide compiled classes of your project with sonar.java

Travis build is hanging waiting for user input (To install angular)

点点圈 提交于 2019-12-02 00:00:40
问题 When building the app with Travis, the build hangs after it tries to install angular. It does this by waiting for input. I have gone through the docs which show that this is indeed the case when "Waiting for keyboard input or other kind of human interaction". But I get no option of doing this anywhere. My .travis.yml is up to date and does what is expected. My .yml code language: node_js node_js: - "11.0" sudo: required branches: only: - master before_script: - npm install -g --silent

Travis build is hanging waiting for user input (To install angular)

核能气质少年 提交于 2019-12-01 20:48:42
When building the app with Travis, the build hangs after it tries to install angular. It does this by waiting for input. I have gone through the docs which show that this is indeed the case when "Waiting for keyboard input or other kind of human interaction". But I get no option of doing this anywhere. My .travis.yml is up to date and does what is expected. My .yml code language: node_js node_js: - "11.0" sudo: required branches: only: - master before_script: - npm install -g --silent firebase-tools - npm install -g @angular/cli script: - npm install - ng build --prod deploy: skip_cleanup:

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

人走茶凉 提交于 2019-12-01 19:54:35
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: Cannot find module 'react-test-renderer/shallow' at Function.Module._resolveFilename (module.js:469:15) at

Run Coverity scan for every Travis pull request build

早过忘川 提交于 2019-12-01 18:15:39
I want to automate student assignment grading system as much as possible. Ideally these steps will be taken when submitting the assignment. Student forks my Github repository and modifies files Student pushes the local code to his repository and creates pull request Travis CI detects pull request and run Pull Request build If code builds successfully, Coverity runs static code analysis for the pull request Student gets build status from the Github pull request page I've successfully set Travis builds for every pull request in my repo. I have successfully run Coverity scan via Travis for every