travis-ci

问题 When building R packages, we use testthat to write tests. We have 2 files: a test file for the specific package ( specific.R ), and one that we use to make sure all packages continue to work together and the overall result is fine ( overall.R ). Both tests are currently run when we push to github or create a PR through Travis, which implicitly runs this line of code( R CMD check *tar.gz ). check runs all the tests in the test folder, and thus both files are run. Now, I'm a bit new to testing.

问题 Are there any cloud CI services that allow Vagrant VMs to run using VirtualBox as a provider? Early investigation shows this seems not to be possible with Travis CI or Circle CI, although the vagrant-aws plugin allows for the use of AWS servers as a Vagrant provider. Is this correct? 回答1: That's right. There are still no CI services allowing to run Vagrant via LXC or Virtualbox (and that's sad). You can't do it under Travis. You can't under CodeShip You can't under CircleCI Don't know about

问题 I'm trying to build android project using Travis using android-28 and build-tools-28.0.0 but no matter what I do I get >Failed to install the following Android SDK packages as some licences have not been accepted. platforms;android-28 Android SDK Platform 28 build-tools;28.0.0 Android SDK Build-Tools 28 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager. Alternatively, to transfer the license agreements from one

问题 I'm trying to build android project using Travis using android-28 and build-tools-28.0.0 but no matter what I do I get >Failed to install the following Android SDK packages as some licences have not been accepted. platforms;android-28 Android SDK Platform 28 build-tools;28.0.0 Android SDK Build-Tools 28 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager. Alternatively, to transfer the license agreements from one

问题 I'm setting up travis-ci to build & push docker images when they are committed to github. But client docker image is not built & pushed to docker hub even though api & nginx images are succeeded. Sorce code is here: https://github.com/jpskgc/article client: react api: golang ci: travis-ci This is .travis.yml language: generic sudo: required services: - docker before_install: - docker build -t jpskgc/react-test -f ./client/Dockerfile.dev ./client script: - docker run -e CI=true jpskgc/react

问题 In a .travis.yml file using sbt, I see this script: - sbt ++$TRAVIS_SCALA_VERSION test:fastOptJS test:fullOptJS In sbt, I can run test , and I can run fastOptJS . What does the single colon between them do? In travis, can one run a sequence of commands? ie. what does it mean for test:fastOptJS to be followed by test:fullOptJS ? 回答1: In sbt, I can run test , and I can run fastOptJS . What does the single colon between them do? test:fastOptJS means fastOptJS in test scope. The confusion comes

问题 In a .travis.yml file using sbt, I see this script: - sbt ++$TRAVIS_SCALA_VERSION test:fastOptJS test:fullOptJS In sbt, I can run test , and I can run fastOptJS . What does the single colon between them do? In travis, can one run a sequence of commands? ie. what does it mean for test:fastOptJS to be followed by test:fullOptJS ? 回答1: In sbt, I can run test , and I can run fastOptJS . What does the single colon between them do? test:fastOptJS means fastOptJS in test scope. The confusion comes

问题 Working on understanding how to go about automated unit testing for PySide2-based applications. However, whenever I attempt to initialize a QApplication instance within the tests, be it through PySide2 itself or through pytest-qt 's qtbot fixture, travis-ci aborts the test. It works locally, however. I've attempted using the qtbot and qapp fixtures from pytest-qt , trying different travis-ci distros like xenial and trusty , as well as including the pytest-xvfb plugin as I've seen recommended

问题 Working on understanding how to go about automated unit testing for PySide2-based applications. However, whenever I attempt to initialize a QApplication instance within the tests, be it through PySide2 itself or through pytest-qt 's qtbot fixture, travis-ci aborts the test. It works locally, however. I've attempted using the qtbot and qapp fixtures from pytest-qt , trying different travis-ci distros like xenial and trusty , as well as including the pytest-xvfb plugin as I've seen recommended

问题 I'm building an R package on Travis to share the integration status with users of the package. I have no errors but 8 warnings and I would like to ignore them for the moment. But travis considered the build a failure and returns the message on the last line of the R CMD check log: Found warnings, treating as errors (as requested) How to ignore warnings? 回答1: All you need to do is have warnings_are_errors: false near the top of your .travis.yml file Here is an example from one of my R packages