travis-ci

问题 I want to use Travis-CI with my Grails 3.0.9 app. For this I created a .travis.yml file: language: groovy jdk: - oraclejdk7 before_install: - curl -s get.sdkman.io | bash - source "$HOME/.sdkman/bin/sdkman-init.sh" - sdk install grails 3.0.9 - sdk default grails 3.0.9 script: grails test-app --stacktrace When the Travis-CI service wants to build my application, it ends up with this error: $ export GRAILS_HOME=/home/travis/.sdkman/candidates/grails/3.0.9/ $ export PATH=$PATH:$GRAILS_HOME/bin $

问题 I'm having trouble encrypting my database.yml for Travis CI. Based on their documentation, it appears you encrypt files with the travis encrypt-file command. I'm running on Ruby-2.2.2 and it's giving me some pretty cryptic error messages. travis encrypt-file config/database.yml --add And I get this error: private method `load' called for Psych:Module for a full error report, run travis report Here's the backtrace when I run travis report : $ travis report /Users/William.Jeffries/.rbenv

问题 I have the following in my tests/conftest.py file, used to load a numpy array as a fixture object for tests that are run by pytest: @pytest.fixture(scope="module") def my_fixture(): return np.load(os.path.join(os.getcwd(), "fixture", "example.npy") The file projectname/tests/fixture/example.npy is present. This runs fine when I launch my tests from PyCharm, but when the tests run on TravisCI I get a file not found error, with the file path shown as missing the tests directory, i.e. it should

问题 I created an API using SlimeFramework then wrote test to see if results returned from the routes are accurate and also to test side effects of accessing these routes. I am making the client call with guzzle. I am required to use continuous integration to send the information to travisCI, but travis does not have a host on which I can test my API, and guzzle requires a client(url) from which to make the route calls. I am new to using any form of continuous integration and do not know what to

问题 According to this question, you need to ssh to the debug build to see the content of secure variables in travis: How I can decrypt secure env variables? I would like to avoid to ssh to the debug build, since I have a public repo and the "ssh to debug build" option is only available for private repos. 回答1: I found a simple way to send me the content of these variables without revealing them to the build result. I added one line to before_install : - curl https://example.com/travis/$encrypted_c

问题 Is there a way to trigger Travis CI build for repository X each time there's a push to repository Y? Specifically, I want my builds to start each time there's a push to http://github.com/tensorflow/tensorflow 回答1: Good question! Here are some solutions that I could think of: If you have admin privileges on the repo (or know someone who does), you could create a webhook that subscribes to the push event and when triggered, start a build on Travis CI using the Travis API. This would entail:

问题 I have a Personal Access Token from Github that I use in many of my projects. Since the token has read/write ability for all my repos, it's important I use the Travis Command Line Tool to encrypt the GITHUB_TOKEN and place it in my .travis.yml as a secure variable: travis encrypt GITHUB_TOKEN=****secret**** --add The Problem The GITHUB_TOKEN value is a hard to remember string of random characters, so every time I need it I first have to go find it, and then copy n' paste it into git bash.

问题 I have a project whose complete source you can find at its GitHub page here on the feat/config branch. The problem I am having is that ClassName.class.getClassLoader().getResourceAsStream() always returns null , and creating a File with the complete path (including the source directory) also returns a FileNotFoundException . This code should load the default configuration values out of a classpath resource and write it to a File . It works locally but fails on Travis CI. public static void

问题 I want to create a yml file to prevent my production code from deploying when a new commit is made to the repo. I only want the production code to be built & deployed if a direct push is made to the master branch . My existing yml config builds & deploys my changes if I create a pull request - without actually merging. I want to stop this. I only want the 'building & deploying' part to be done after a pull request has been made and changes are actually pushed into master . This is what my

问题 I m trying to use travis CI with nodejs and I m facing a problem like this one. What I want here, is only to use ftp to upload my file, not to run any command. No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb) I dont know what is the problem actually... Here's my travis.yml file : env: global: - "FTP_USER=xxx" - "FTP_PASSWORD=xxx" after_success: "curl --ftp-create-dirs -T uploadfilename -u $FTP_USER:$FTP_PASSWORD ftp://xxxx.fr/www/mochatest" What am I doing wrong ?