travis-ci

After updating my Haskell package's .cabal file to Cabal 2.2 , most of my Travis CI builds with resolvers older than LTS 12.9 fail with: This package description follows version 2.2 of the Cabal specification. This tool only supports up to version XX.XX.XX. where the version varies depending on the resolver specified in my .travis.yaml . It seems that for each resolver I need to specify a different Cabal version In fact, because of Cabal spec changes, I appear to need a different .cabal file for each resolver. Is this the case? Is there a better way? How do I match the right Cabal spec with

I'm trying to use Travis CI for my Android Project but my Builds constantly failing but works on local build. I am using Android Studio Preview 3 and gradle 3 alpha 3. I am getting this error below. Could not find com.android.tools.build:gradle:3.0.0-alpha3. Here is my build log My Travis Config file My Project gradle file I'm getting an Access denied error to your build log , and I didn't use it, but I'll try to answer you. As announced here : The Android Gradle Plugin 3.0.0-alpha3 was also released through maven.google.com. You can try to fix it by adding Google’s Maven Repository here like

Need a .travis sample yaml file for unit testing mysql queries on Django. This is a sample .travis.yaml for Django unit testing with MySQL integration. language: python python: # - "2.6" - "2.7" services: mysql env: # - DJANGO=1.2.7 # - DJANGO=1.3.1 - DJANGO=1.4.3 DJANGO_SETTINGS_MODULE="mysite.travis_settings" install: - pip install -q Django==$DJANGO --use-mirrors - pip install pep8 --use-mirrors - pip install mysql-python --use-mirrors # - pip install https://github.com/dcramer/pyflakes/tarball/master # - pip install -q -e . --use-mirrors before_script: # - "pep8 --exclude=migrations -

I'm trying to get a Travis CI build to work in both my own private fork and the repo of my organization. I encrypted a config file using the travis encrypt-file command and it seems to have created two environment variables in the travis settings for my own fork that look like: "encrypted_d1234_key" and "encrypted_d1234_iv". These are used when the build runs to decrypt the config file, like so: openssl aes-256-cbc -K $encrypted_d1234_key -iv $encrypted_d1234_iv -in test.config.enc -out test.config -d Can I somehow copy those secure environment variables over to the settings for my org's repo

I have forked a Github repository and would like to use travis-ci, as the original repository does, to run tests when I commit. However, the AWS keys, which are encrypted , are not decrypted and keep the tests from succeeding. Since my workplace owns the original repository, I have access to whatever is needed, but am unsure what information to retrieve, where to find it, or what to do with it. For clarity, here is the pertinent part of the .travis.yml: env: global: - NODE_ENV: test - [...] - secure: M3YSEJnWYd[...] - secure: kvvLABsWTq[...] All of the environment variables are imported except