travis-ci

Travis CI testing branches with corresponding set of environment variables

倾然丶 夕夏残阳落幕 提交于 2019-12-04 01:03:27
问题 I have a project that I'm trying to automate tests using Travis CI. I have a dev branch and a test branch, and they have different environment variables. For example, on the dev branch, I need to connect to a different API than the test branch, specified by an environment variable. So, when I run the build on the dev branch on Travis, how do I set it up so that it only tests with the dev set of environment variables, and likewise for build on test branch? 回答1: There is no great way to do this

Travis-CI skipping deployment although Commit is tagged

五迷三道 提交于 2019-12-04 00:41:54
I'm quite new to Travis CI, but I found my way through it using their docs. However deploying to GitHub releases doesn't work for me. My .travis.yml file looks like this: language: java branches: only: - master notifications: email: false before_deploy: - export RELEASE_JAR_FILE=$(ls build/libs/*.jar) - echo "Deploying $RELEASE_JAR_FILE to GitHub" deploy: provider: releases api_key: secure: [key] file_glob: true file: "${RELEASE_JAR_FILE}" skip_cleanup: true on: repo: [my-repo] tags: true all_branches: true Here's how I commit: $ git add . && git commit -m "my message" $ git tag 0.1234 $ git

How I can decrypt secure env variables?

回眸只為那壹抹淺笑 提交于 2019-12-03 22:18:37
I have .travis.yml with some secure (encrypted) env variables. Now I need to descrypt those variables to use them in different project. Is there easy way of doing this (except triggering a commit and printing them in console output)? I don't think you can decrypt it. Public key is used to encrypt the data and it can only be decrypted with the private key which travis doesn't provide. You can't decrypt locally from what I understand but you can recover the key/values. By nature, they have to be decrypted to be used during the build process. Go to your last build of your current project. Select

Rake db:test:prepare task deleting data in development database

六眼飞鱼酱① 提交于 2019-12-03 17:52:17
问题 Using a simple Rails sqlite3 configuration example in my config/database.yml for a Rails 3.2.6 app, I used to reset my development database, re-seed it, and prepare my test database simply by performing: $ rake db:reset $ rake db:test:prepare After looking at this blog entry about testing a Rails application with Travis CI on different database engines, I thought I'd give it a try, so I installed mysql and postgresql using Homebrew (I'm on OSX Snow Leopard), set them up as per the brew info

How to disable Android emulator animations in Travis?

两盒软妹~` 提交于 2019-12-03 17:26:20
I am running Espresso tests in the Travis CI. When I run my tests in my device, I normally disable all my animations so I don't have to use Thread.sleep all the time. But I really don't know how to do this in the Travis CI, so my tests fail without the Thread.sleep. I looked over the internet... but I didn't find any tutorial about how to do disable the animations in the emulator I could use idling resource in Espresso, I know. But some times I would prefer not to. albodelu If you try @azizbekian's path, I wrote about this here , created new test rules here and tested it here I confirm

How can I update full description on Docker Hub automatically?

﹥>﹥吖頭↗ 提交于 2019-12-03 17:26:14
问题 I'm using Travis CI for building docker images from Dockerfiles and then pushing them to the Docker Hub on success. I've created an MD file describing the image and how to use it. I want to have the same description on the Docker Hub in the full description section. As I may update the description in the future, I want to have Travis CI automatically update the description based on the MD file in the repository with the new image. Anyone knows how to do this? 回答1: Since the Docker Hub does

Install ruby headers with rvm

点点圈 提交于 2019-12-03 17:23:14
Travis CI uses RVM to provide Ruby, but it doen't seem to contain the headers: $ find /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux/zlib.so /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux/dl.so /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux/syck.so /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux/socket.so /home/vagrant/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/i686-linux/dbm.so

TravisCI / Coverity: Warning - No files were emitted

半城伤御伤魂 提交于 2019-12-03 17:12:46
I have a medium size github repository for which I configured Travis-CI/Coverity tools. About a month ago my setup had worked just fine: Travis compiled and built my application, and then performed the Coverity scan and I could see the results on my Coverity page. However, lately, the Coverity analysis stopped working. I looked through the Travis log files and compared to the old logs when the builds were successful and that's what I found: At the end of the log, the failed version contains the next warning: [WARNING] No files were emitted. This may be due to a problem with your configuration

Travis CI for Android

强颜欢笑 提交于 2019-12-03 16:23:09
问题 Trying to get started with Travis CI for my Android projects. First I set up dummy project with Android Bootstrap, and added a the yml file from square's otto project - modified to have my username and repo name. My build fails with the error "/home/travis/build.sh: line 94: android: command not found, even when square's project builds fine. The error seems to indicate that the path isn't set properly, in spite of having these lines in my .travis.yml export ANDROID_HOME=~/builds/f2prateek

Getting TravisCI to commit and push a modified file with Tags (releases)

孤街醉人 提交于 2019-12-03 16:20:09
I was helped by Sir Athos (thank you greatly) earlier today on a separate question which helped me greatly. I am now stuck at a point where I want to modify a simple text file and include it in my push. So basically I want to add the modified text file to a commit and push it as a commit with it's build number tag as a release. Hope I am making sense here. My code to do try and do this so far is #!/bin/bash YEAR=$(date +"%Y") MONTH=$(date +"%m") git config --global user.email "${GIT_EMAIL}" git config --global user.name "${GIT_NAME}" git config --global push.default simple export GIT_TAG=v2.