travis-ci

I have created a simple travis configuration which packages an app and tries to deploy the archive file to github. The problem is, I would like to have the version number part of the file name, so i require to use a pattern for the filename. I simply can't get it to work. Configuration is currently: deploy: provider: releases file: "build/distributions/worktrail-app-hub-sync*.zip" on: repo: worktrail/worktrail-app-hub-sync tags: true all_branches: true But it fails with: "/home/travis/.rvm/gems/ruby-1.9.3-p547/gems/octokit-3.3.1/lib/octokit/client/releases.rb:86:in `initialize': No such file

I want to use apt to install some packages for the test, however, it fails due to that the sudo is disabled. I found the following in the test output: Sudo, the FireFox addon, setuid and setgid have been disabled. It seems that the output comes from this line in travic-ci , but setting paranoid_mode to false in .travis.yml does not work. How to enable sudo access? PS: I am using private repo. EDIT: The following .travis.yml will fail due to sudo: must be setuid root when running sudo apt-get update -qq language: python python: - "3.4" before_install: - sudo apt-get update -qq script: -

I have a Travis CI build that produces more than 4MB of output which exceeds Travis CIs limit. I have tried sending output to /dev/null, but Travis also fails if no output is seen for 10 minutes How can I workaround these constraints? The following script sends some dummy output to keep the build alive but also records the build output to a file and displays a tail of the output if the build returns an error: #!/bin/bash # Abort on Error set -e export PING_SLEEP=30s export WORKDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" export BUILD_OUTPUT=$WORKDIR/build.out touch $BUILD_OUTPUT

I have been attempting to have Travis-CI automatically post its build product on GitHub Releases whenever a commit is pushed to [master]. Unfortunately, GitHub Releases requires a tag to release with. As a solution, I attempted to have Travis automatically generate and apply a tag to the commit. However, every time Travis updates the repository, it causes the release to fail. As such, what am I doing wrong with my current setup and|or is there a way to do what I have described. My travis.yml: language: java before_install: chmod +x gradlew install: true matrix: include: - jdk: oraclejdk8

In my github repo's readme.md file I have a Travis-CI badge. I use the following link: https://travis-ci.org/joegattnet/joegattnet_v3.png?branch=staging The obvious problem is that the branch is hardcoded. Is it possible to use some sort of variable so that the branch is the one currently being viewed? VonC Not that I know of. GitHub support confirms (through OP Joe Gatt 's comment ) The only way to do this would be to pass the link through my own service which would use the github's http referrer header to determine which branch is being referenced and then fetch the appropriate image from

There is any way to deploy a heroku rails app after a travis-ci success build? Travis CI now has built-in support for deploying to Heroku: http://about.travis-ci.org/blog/2013-07-09-introducing-continuous-deployment-to-heroku/ Odi I just implemented this case with an application of mine. It's actually not that hard to do, but it requires some steps: You need your heroku API key See this gist for an example .travis.yml and get the travis_deployer.rb script Then install the travis gem, see the answer to another question on how to secure your API key . If you don't care about it, just use the

We are compiling Doxygen docs on the travis-ci server and want to push them onto our gh-pages branch. How do I handle the authorization for git push ? Does someone have an example for using encrypted variables in travis-ci? Should I go for https authorization or for an SSH key? Step-by-step example with HTTPS API Token in environment variable Others have mentioned it, but here goes a more detailed procedure. Create a separate repository for the website (optional). This will reduce the likelihood that you overwrite your main repository, and will keep output files from polluting it. Get a

I have a stage test and production . I would like to manually confirm the deployment to production. Is there way to achieve this? You can make use of Conditional Deployments . This allows you to specify whether you push to production or test . Combine it with e.g. a check-live-deployment.sh -script and differentiate between branches and/or tagged commits. For example: #!/bin/bash set -e contains() { if [[ $TRAVIS_TAG = *"-live"* ]] then #"-live" is in $TRAVIS_TAG echo "true" else #"-live" is not in $TRAVIS_TAG echo "false" fi } echo "============== CHECKING IF DEPLOYMENT CONDITION IS MET =====