travis-ci

Travis CI: PHP 7.2 don't support Argon2i

﹥>﹥吖頭↗ 提交于 2019-12-04 19:28:51
I've an error in my project with Travis CI: Argon2i algorithm is not supported. Please install the libsodium extension or upgrade to PHP 7.2+. But, Argon2i is present in the PHP 7.2 version and Travis CI install the PHP 7.2 version: $ phpenv global 7.2 2>/dev/null 7.2 is not pre-installed; installing Downloading archive: https://s3.amazonaws.com/travis-php-archives/binaries/ubuntu/14.04/x86_64/php-7.2.tar.bz2 $ curl -s -o archive.tar.bz2 $archive_url && tar xjf archive.tar.bz2 --directory / $ phpenv global 7.2 $ php --version PHP 7.2.0 (cli) (built: Dec 2 2017 17:12:55) ( ZTS ) Copyright (c)

travis.ci keeps on failing when running “bundle exec rake”

末鹿安然 提交于 2019-12-04 18:44:59
I am trying to get automated testing sorted out with Travis.ci. However, at the moment the build keeps on failing when trying to execute bundle exec rake . This is what I see... $ bundle exec rake rake aborted! Don't know how to build task 'default' /home/travis/.rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `eval' /home/travis/.rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `<main>' (See full trace by running task with --trace) The command "bundle exec rake" exited with 1. Done. Your build exited with 1. My unit tests are in the test folder in the main directory and is named

undefined reference to `std::__cxx11::basic_string in Boost on Travis CI

天涯浪子 提交于 2019-12-04 18:41:46
I am trying to get a C+++ project which uses Boost on GitHub to compile correctly on Travis CI. First I tried the packages and PPAs on ubuntu, but they were too old(I need at least Boost 1.61). I got it to work only if I compiled Boost on Travis CI(download, compile), but, unfortunately, the compile time is big (11-18 mins) and the log file is just huge. Thinking how to get over this issues, I thinked about compiling boost on my machine, zipping, uploading to some web server and just downloading and copying on /usr/local/[include/lib] the corresponding files. Here is the compiler I used on my

Error: TSError: ⨯ Unable to compile TypeScript

一世执手 提交于 2019-12-04 18:07:05
问题 I am facing the problem: My Project is built on Angular4 with typescript, e2e testing with protractor & karma. Travis-ci has this error: [03:34:54] E/launcher - Error: TSError: ⨯ Unable to compile TypeScript Cannot find type definition file for 'jasmine'. (2688) Cannot find type definition file for 'node'. (2688) e2e/app.e2e-spec.ts (1,32): Cannot find module './app.po'. (2307) e2e/app.e2e-spec.ts (4,1): Cannot find name 'describe'. (2304) e2e/app.e2e-spec.ts (7,3): Cannot find name

TravisCI: Run after_success on a specific branch

给你一囗甜甜゛ 提交于 2019-12-04 16:45:11
问题 I would like to know how to run an after_success script only for a specific branch. I am using a custom script to deploy the app after build passes. I would only like to run this when on prod branch. So far, I have tried the following: #1 after_success: - # some deployment script on: prod #2 branches: only: - prod after_success: - # some deployment script #3 after_success: branches: only: - prod - # some deployment script Any suggestions? 回答1: I solved it by writing a simple script using

Travis-CI is unable to open file

南楼画角 提交于 2019-12-04 16:40:52
I'm trying to build my iOS project, but travis-ci is printing following error message: /Users/travis/build/BilalReffas/Analyzer/Pods/Pods/Target Support Files/Pods-Analyzer/Pods-Analyzer.debug.xcconfig: unable to open file (in target "Analyzer" in project "Analyzer") (in target 'Analyzer') Of course I selected my scheme as shared. It's possible for me to build the project locally. I don't understand why travis is not finding the debug.xcconfig file. My Podfile: platform :ios, '10.0' target 'Analyzer' do use_frameworks! pod 'Charts' end My travis.yml: language: objective-c osx_image: xcode10

cryptography AssertionError: sorry, but this version only supports 100 named groups

痞子三分冷 提交于 2019-12-04 16:35:32
问题 I'm installing several python packages via pip install on travis, language: python python: - '2.7' install: - pip install -r requirements/env.txt Everything worked fine, but today I started getting following error: Running setup.py install for cryptography Traceback (most recent call last): File "<string>", line 1, in <module> File "/tmp/pip-build-hKwMR3/cryptography/setup.py", line 334, in <module> **keywords_with_side_effects(sys.argv) File "/opt/python/2.7.9/lib/python2.7/distutils/core.py

“ERROR: Unexpected action: build” when building a project with Swift 3 and Cocoapods on Travis-CI

我怕爱的太早我们不能终老 提交于 2019-12-04 16:20:27
问题 Evening/morning/afternoon all, Been hitting my head over this for a bit now and couldn't find anything online about this so my best bet is here. When Travis-CI builds my project I get the following error: xctool -workspace Project.xcworkspace -scheme ProjectTests build test ERROR: Unexpected action: build and here is my config: language: objective-c xcode_workspace: Project.xcworkspace xcode_scheme: ProjectTests osx_image: xcode8.2 Perhaps I missed something in the tutorial? I got a little

GitHub and Travis CI - How to fail build when tests fail

南笙酒味 提交于 2019-12-04 15:44:36
I have a Scala project on GitHub and I use the Travis CI to build it and show the resulting badge on the project home in GitHub. I started to write unit tests and I realized that during one of my commit, some tests failed. But the travis build shows that the build passes. I know that I should be using some kind of hook to check for tests failures and correspondingly fail my build. But I just don't know what the correct command for that is? I could not as well infer this from any documentation. Here is my travis.yml file: language: scala jdk: - oraclejdk8 scala: - 2.11.7 script: - sbt clean

TravisCI: How to allow failures for environment variable

荒凉一梦 提交于 2019-12-04 15:18:35
问题 How to allow failures for builds having specific environment variable value? For example: .travis.yml: env: - TEST_GROUP=Smoke - TEST_GROUP=other # How to allow failures for this variable? matrix: allow_failures: - TEST_GROUP=other # This does not work 回答1: You need to explicitly reference env in the allow_failures section: matrix: allow_failures: - env: TEST_GROUP=other 回答2: @roidrage's answer works for me. When using multiple env variables in a single matrix dimension, env variables have to