I have a github repository `user/repo` but the real project is in a subfolder `user/repo/project/build.sbt`  
What should I write in the `.travis.yml` to make Travis ignore the top folder and work only in the project folder?

Inspired by [this](https://stackoverflow.com/questions/14006810/how-do-i-get-travis-build-working-directory-in-travis-yml) I tried the following which didn&#39;t work:

    env:
      global:
        - REPO=&quot;user/repo&quot;
        - CI_HOME=`pwd`/$REPO
    script: sh -c &#39;cd $CI_HOME/project&#39; &amp;&amp; sbt ++$TRAVIS_SCALA_VERSION package

Error log:

    $ sh -c &#39;cd $CI_HOME/project&#39; &amp;&amp; sbt ++$TRAVIS_SCALA_VERSION package
    Detected sbt version 0.12.2-RC1
    /home/travis/build/user/repo doesn&#39;t appear to be an sbt project.

Ideally there should be a way to specify the build folder but let Travis handle the build command.

How to specify a build folder in Travis?

I would like to use [Travis CI](http://travis-ci.org/) for my open-source project. The issue that Travis doesn&#39;t provide any ways to publish produced artifacts (though, they have this in their future plans).

What are workarounds to publish/upload artifacts somewhere? I&#39;m allowed to execute any scripts on a CI machine.

Simple upload will work, but there is security issue: anyone will be able to upload something in the same way as all sources are public.



How to publish artifacts in Travis CI?

I have a spring boot project here: https://github.com/jcasbin/jcasbin-springboot-plugin. I encountered [the following error in Travis CI](https://travis-ci.org/jcasbin/jcasbin-springboot-plugin/jobs/373086014):

    shell
    3.43s$ ./mvnw install -DskipTests=true -Dmaven.javadoc.skip=true -B -V
    /home/travis/build/jcasbin/jcasbin-springboot-plugin
    Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m
    Error: Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain
    The command &quot;eval ./mvnw install -DskipTests=true -Dmaven.javadoc.skip=true -B -V &quot; failed. Retrying, 2 of 3.

It seems that the `mvnw` command fails. This file is generated by my IDE:  IntelliJ IDEA 2018.1. I don&#39;t know what it is used for and why does it fail?

I already fired an issue in Spring Boot&#39;s github issues [here](https://github.com/spring-projects/spring-boot/issues/13002), but Spring project said it&#39;s Maven wrapper&#39;s issue and pointed me here. I don&#39;t quite understand what it means. Is it a Maven bug? How to fix the error then? 

Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain

For my project I need to choose between Jenkins and Travis-CI. I’ve been using Jenkins for years but I’ve also read good reviews about Travis-CI.

Which one would you use for an Open Source project? What are the main benefits or advantages of both?

Jenkins vs Travis-CI. Which one would you use for a Open Source project?

I have `travis-ci` integrated with my GitHub account (https://github.com/pradeep0601/Angular5-Router-App).

When I updated `@angular/cli` version from 1.7.4 to 6.0.0-rc.3, the build started failing with an error:

    Local workspace file (&#39;angular.json&#39;) could not be found.
    Error: Local workspace file (&#39;angular.json&#39;) could not be found.
        at WorkspaceLoader._getProjectWorkspaceFilePath (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/workspace-loader.js:37:19)
        at WorkspaceLoader.loadWorkspace (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/workspace-loader.js:24:21)
        at TestCommand._loadWorkspaceAndArchitect (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/architect-command.js:177:32)
        at TestCommand.&lt;anonymous&gt; (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/architect-command.js:45:25)
        at Generator.next (&lt;anonymous&gt;)
        at /home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/architect-command.js:7:71
        at new Promise (&lt;anonymous&gt;)
        at __awaiter (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/architect-command.js:3:12)
        at TestCommand.initialize (/home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/architect-command.js:44:16)
        at /home/travis/build/pradeep0601/Angular5-Router-App/node_modules/@angular/cli/models/command-runner.js:100:23

package.json snippet to better understand the running environment:

        &quot;@angular/cli&quot;: &quot;6.0.0-rc.3&quot;,
        &quot;@angular/compiler-cli&quot;: &quot;^5.2.0&quot;,
        &quot;@angular/language-service&quot;: &quot;^5.2.0&quot;,
        &quot;@types/jasmine&quot;: &quot;~2.8.3&quot;,
        &quot;@types/jasminewd2&quot;: &quot;~2.0.2&quot;,



Error: Local workspace file (&#39;angular.json&#39;) could not be found

My Python package has a `setup.py` which builds fine locally on Ubuntu Trusty and on a fresh Vagrant Ubuntu Trusty VM when I provision it like this:

    sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
    curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
    sudo -H pip install setuptools wheel virtualenv --upgrade

But when I do the same on a Travis CI Trusty Beta VM:

    - sudo apt-get install python python-dev --force-yes --assume-yes --fix-broken
    - curl --silent --show-error --retry 5 https://bootstrap.pypa.io/get-pip.py | sudo python2.7
    - sudo -H pip install setuptools wheel virtualenv --upgrade

I get:

    python2.7 setup.py bdist_wheel
    usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
       or: setup.py --help [cmd1 cmd2 ...]
       or: setup.py --help-commands
       or: setup.py cmd --help
    error: invalid command &#39;bdist_wheel&#39;

This https://stackoverflow.com/questions/26664102/why-can-i-not-create-a-wheel-in-python is related but note I am installing wheel and upgrading setuptools.

Why is python setup.py saying invalid command &#39;bdist_wheel&#39; on Travis CI?

Using **Travis CI** for an existing Android project calling 

    $ ./gradlew build connectedCheck

 I get this error:

    /home/travis/build.sh: line 45: ./gradlew: Permission denied
    The command &quot;./gradlew build connectedCheck&quot; failed and exited with 126 during .


Travis.yml ./gradlew : Permission denied

I remember recently seeing the Travis build status of a pr or commit in GitHub browsing the repository (but can&#39;t find where). I&#39;m not talking about the Travis build status images in `README.md` but an actual GitHub feature (green box with a friendly check mark).

While my commits build on Travis just fine I&#39;d like to get the results displayed in GitHub (which they don&#39;t do right now). I&#39;d like to know how to enable this. 

*UPDATE*

Found an [example here](https://github.com/sebastianbergmann/phpunit/pull/1051/commits) - see the small green check mark saying &quot;Travis-CI build passed&quot;?

Showing Travis build status in GitHub repo

I&#39;ve just joined a project, and I&#39;m new to travis-ci.  I&#39;d rather not have to push every little change to `.travis.yml` and every little change I make to the source in order to run the build.  With jenkins you can download jenkins and run locally.  Does travis offer something like this?

&gt; Note: I&#39;ve seen the travis-ci cli and downloaded it, but all it seems
&gt; to do is call their API, which then connects to my GitHub repo, so if
&gt; I don&#39;t push, it won&#39;t matter that I restart the last build.



How to run travis-ci locally

In my github repo&#39;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?

Referencing current branch in github readme.md

&lt;!-- language-all: lang-yml --&gt;

My project uses both nodejs and java

I tried starting off with a node_js build then installing java (since this is an npm module)

but the scripts to install java failed, plus I don&#39;t think there&#39;s a need to install it when there is a build with java that already exists.

should I start off with a java build then install node?

I&#39;m trying this

    language: java
      - oraclejdk8
    language: node_js
    node_js:
      - &quot;0.10&quot;

which ignores the first 2 lines it seems and builds a node_js build which has java 7
and my project uses java 8

I tried this [answer](https://stackoverflow.com/questions/27036259/how-to-write-travis-yml-if-my-project-deps-on-python-and-nodejs) for python

using 

    language: node_js
    node_js:
      - &quot;0.10&quot;
    java: oraclejdk8

but that didn&#39;t work

How can I add java 8?


How to set up Travis CI with multiple languages

I&#39;d like to use [travis-ci][1] for one of my [projects][2].

The project is an API wrapper, so many of the tests rely on the use of secret API keys. To test locally, I just store them as environment variables. What&#39;s a safe way to use those keys on Travis?


  [1]: http://travis-ci.org/
  [2]: https://github.com/adelevie/parse-ruby-client

Using secret api keys on travis-ci

Travis CI continuous integration service officially supports many [languages](http://about.travis-ci.org/docs/#Specific-Language-Help), but not C# or F#. 

Can I use it with my .net projects?

How do I use Travis-CI with C# or F#

I am very new to Git and I am planning to contribute to some open-source project on GitHub after discovering a small error in it. Upon forking it and fixing the error, I purposed a pull request and I noticed this showing up:  

&gt; Failed — The Travis CI build failed

Looking into the details I discovered it was caused by `Could not find .travis.yml`, which made perfect sense since I had not signed in to Travis Cl with and add .travis.yml to the repository.

This is my first time hearing about Travis and what that is known as continuous integration. And it sounds pretty cool so in order to learn more about it, I looked it up on Wikipedia.


&gt;  Travis CI is a hosted, distributed continuous integration service
&gt; used to build and test projects hosted at GitHub. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to **build the project and run tests**. This includes commits to all branches, not just to the master branch.

My current understanding of Travis CI is that what it does is automatically pushing the project upon `git commit -am &quot;..&quot;` and I don&#39;t quite understand some part of it.

1. By **building the project and run tests**, what tests is it going to run? And how is it going to &quot;build&quot; the project? (like compiling it to binary?)

2. It states that &quot;This includes commits to all branches&quot; - but what if I don&#39;t want to commit to all branches?

3. Is it alright if I don&#39;t use Travis Cl at all? Under what circumstances is it best to use it (or it must be used)? 


Trying to understand what Travis CI does and when it should be used

Inside the `.travis.yml` configuration file what is the practical difference between `before_install`, `install`, `before_script` and `script` options?

I have found no documentation explaining the differences between these options.

What are the differences between the {before_,}{install,script} .travis.yml options?

I can&#39;t run my test case due to this following errors : 

 - The bundle “UITests” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle.
 - Library not loaded: @rpath/Alamofire.framework/Alamofire.
 - Reason: image not found

Try searching and solving since two days but couldn&#39;t get through this issue can someone please help. 




The bundle UITests couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle

Using Travis-CI, is it possible to trigger a rebuild without pushing a new commit to GitHub?

Use case: A build fails due to an externality. The source is actually correct. It would build OK and pass if simply re-run.

For instance, an `apt-get` fails due to a package server being down, but the server is back up again. However the build status is &quot;stuck&quot; at &quot;failed&quot; until a new commit is pushed.

Is there some way to nudge Travis-CI to do another build, other than pushing a &quot;dummy&quot; commit?

Trigger a Travis-CI rebuild without pushing a commit?

```BASH
$ ./build.sh --quiet verify

/home/travis/build.sh: line 59: ./build.sh: Permission denied. 

The command &quot;./build.sh --quiet verify&quot; exited with 126. 
```

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/ifc2w.png

Permission denied for build.sh file

To put it in &quot;BDD&quot; terms:

&gt; Background: &lt;br/&gt;
Given I&#39;m contributing to a GH repo&lt;br/&gt;

&gt; When I create a pull request&lt;br/&gt;
Then Travis should build the latest commit

&gt; When I push to an existing pull request&lt;br/&gt;
Then Travis should build the latest commit

&gt; When I merge a pull request to master &lt;br/&gt;
Then Travis should build master


I was confused by Travis-CI&#39;s &quot;build pushes&quot; and &quot;build PRs&quot; settings, as:
 
- Enabling both causes each Pull Request to be build twice by Travis
 - once for the commit on that branch
 - and once again for the merge commit of that branch into its destination
- Enabling just &quot;build PRs&quot; causes PRs to be built, but doesn&#39;t result in post-merge builds (i.e. on master).
- Enabling &quot;pushes&quot; brute-force satisfies the above criteria by building _all_ pushes to the repo. You can try to finagle things by white- &amp; black-listing branches, but that will probably bite you unless you&#39;re rigorously disciplined with branch names.

This is explained more in [Travis-CI docs](http://docs.travis-ci.com/user/pull-requests/) and [GH issue #3241](https://github.com/travis-ci/travis-ci/issues/3241).

Anyone know a configuration that satisfies the above criteria?

How to configure Travis-CI to build pull requests &amp; merges to master w/o redundancy

With the release of Xcode 8, Apple introduced a new way of managing the signing configuration. Now you have two options `Manual` and `Automatic`.

According to the WWDC 2016 Session about Code signing [(WWDC 2016 - 401 - What&#39;s new in Xcode app signing)][1], when you select `Automatic` signing, Xcode is going to:

- Create signing certificates
- Create and update App IDs
- Create and update provisioning profiles

But according to what Apple says in that session, the `Automatic Signing` is going to use `Development signing` and will be limited to Xcode-created provisioning profiles.

The issue comes when you try to use `Automatic Signing` on a CI environment (like Travis CI or Jenkins). I&#39;m not able to figure out an easy way to keep using Automatic and sign for Distribution (as Xcode forces you to use Development and Xcode-created provisioning profiles).

The new &quot;Xcode-created provisioning profiles&quot; do not show up in the developer portal, although I can find then in my machine... should I move those profiles to the CI machine, build for `Development` and export for `Distribution`? Is there a way to override the `Automatic Signing` using `xcodebuild`?


  [1]: https://developer.apple.com/videos/play/wwdc2016/401/

Use xcodebuild (Xcode 8) and automatic signing in CI (Travis/Jenkins) environments

I created a Travis CI test using a Github repository. I can&#39;t seem to find any information about how to remove it from the Travis CI test page. Is this at all possible?

How do you remove a Github repository for Travis CI tests?

When working with the .travis.yml, is there an environment variable that contains the name of the current build directory in Travis-CI?  Looking through the docs [here][1] I don&#39;t see one.


  [1]: http://about.travis-ci.org/docs/user/ci-environment/#Environment-variables

How do I get Travis&#39; build working directory in .travis.yml?

I am seeing a build failure on travis-ci, which I cannot reproduce on my local machine.  Are there instructions somewhere for setting up a VM that is identical to the travis-ci linux build environment? I&#39;m glad to have travis-ci already reveal a new bug, but less excited to debug it by sending in commits that add debug code.

How to reproduce a travis-ci build environment for debugging

I can find the current git branch name by doing either of these:

    git branch | awk &#39;/^\*/ { print $2 }&#39;
    git describe --contains --all HEAD

But when in a detached HEAD state, such as in the post build phase in a [Jenkins][1] maven build (or in a Travis git fetch), these commands doesn&#39;t work.

My current working solution is this:

    git show-ref | grep $(git log --pretty=%h -1) | sed &#39;s|.*/$.*$|\1|&#39; | sort -u | grep -v HEAD

It displays any branch name that has the last commit on its HEAD tip.  This works fine, but I feel that someone with stronger git-fu might have a prettier solution?

  [1]: http://jenkins-ci.org/

How to find the current git branch in detached HEAD state

I&#39;m using [Travis-CI][1] to provide continuous integration builds for a few Java open source projects I&#39;m working on.

Normally this works smoothly, but I have a problem when the POM specifies GPG signing, e.g. 

    &lt;plugin&gt;
      &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
      &lt;artifactId&gt;maven-gpg-plugin&lt;/artifactId&gt;
      &lt;version&gt;1.4&lt;/version&gt;
      &lt;executions&gt;
        &lt;execution&gt;
          &lt;id&gt;sign-artifacts&lt;/id&gt;
          &lt;phase&gt;verify&lt;/phase&gt;
          &lt;goals&gt;
            &lt;goal&gt;sign&lt;/goal&gt;
          &lt;/goals&gt;
        &lt;/execution&gt;
      &lt;/executions&gt;
    &lt;/plugin&gt;

This causes the Travis build to fail - apparently because it does not have a passphrase available while running `mvn install`. See [this build][2] for an example.

What is the best way to configure Maven and/or Travis to skip GPG signing for CI test builds, but still perform GPG signing when I do a proper release build?


  [1]: https://travis-ci.org/
  [2]: https://travis-ci.org/nuroko/nurokore/jobs/4683227

Suppressing GPG signing for Maven-based continuous integration builds (Travis CI)

I have a repository that uses `Travis CI`, and in the `.travis.yml` there I have this line:

    script:
    - vim -Nu &lt;(cat &lt;&lt;-EOF
      set nocompatible |
      filetype off
      EOF
      ) -c &#39;Script&#39; &gt; /dev/null

Sadly this doesn&#39;t work, as this is transformed into a single line and is executed like this:

    vim -Nu &lt;(cat &lt;&lt;-EOF set no compatible | filetype off | EOF ) -c &#39;Script&#39; &gt; /dev/null

This makes the `EOF` tag not working, as `EOF` needs to be in a single line.
An alternative would be to just use normal quotes like this:

    script:
    - vim -Nu &lt;(cat &#39;set nocompatible |
      filetype off
      ) -c &#39;Script&#39; &gt; /dev/null

Which works, and is fine, but I feel there must be a way to insert newlines into a `.travis.yml`. I have an alternative now, but I may not in the future. So how do you do it?

How to use multiline command in &#39;script:&#39; with YAML?

I&#39;m having trouble building my nuxt images in a travis CI pipeline. My local environment is ubuntu 18.04 - docker version 19.03.11 docker-compose version 1.24.1 I&#39;m able to build and run my images locally but on the travis CI I get the following error

```
Step 5/7 : RUN npm run build
 ---&gt; Running in d3e9433b79f0
&gt; nuxt_app@1.0.0 build /app
&gt; nuxt build
ℹ Production build
✔ Builder initialized
✔ Nuxt files generated
ℹ Compiling Client
ℹ Starting type checking service...
ℹ Using 1 worker with 2048MB memory limit
✔ Client: Compiled with some errors in 1.62s
Hash: 1b9cf81215d31b9f0ed3
Version: webpack 4.43.0
Time: 1624ms
Built at: 06/07/2020 2:20:27 PM
                  Asset      Size  Chunks               Chunk Names
4bff68cc9fb4c003b7f2.js  1.49 KiB       1  [immutable]  runtime
b4f22db01be076446c20.js   1.4 KiB       0  [immutable]  app
Entrypoint app = 4bff68cc9fb4c003b7f2.js b4f22db01be076446c20.js
ERROR in ./.nuxt/client.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No &quot;exports&quot; main resolved in /app/node_modules/@babel/helper-compilation-targets/package.json
    at applyExports (internal/modules/cjs/loader.js:491:9)
    at resolveExports (internal/modules/cjs/loader.js:507:23)
    at Function.Module._findPath (internal/modules/cjs/loader.js:635:31)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:953:27)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.&lt;anonymous&gt; (/app/node_modules/@babel/preset-env/lib/debug.js:8:33)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.&lt;anonymous&gt; (/app/node_modules/@babel/preset-env/lib/index.js:11:14)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
 @ multi ./.nuxt/client.js app[0]
 FATAL  Nuxt build error
  at WebpackBundler.webpackCompile (node_modules/@nuxt/webpack/dist/webpack.js:5326:21)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)
  at async WebpackBundler.build (node_modules/@nuxt/webpack/dist/webpack.js:5275:5)
  at async Builder.build (node_modules/@nuxt/builder/dist/builder.js:5598:5)
  at async Object.run (node_modules/@nuxt/cli/dist/cli-build.js:100:7)
  at async NuxtCommand.run (node_modules/@nuxt/cli/dist/cli-command.js:2575:7)
```

My travis CI 

```
sudo: required

dist: trusty

services:
    - docker

# language: node_js
# node_js: 12

before_install:
    - sudo rm /usr/local/bin/docker-compose
    - sudo curl -L &quot;https://github.com/docker/compose/releases/download/1.24.0/docker-compose-$(uname -s)-$(uname -m)&quot; -o /usr/local/bin/docker-compose
    - sudo chmod +x /usr/local/bin/docker-compose
    - sudo ln -s /usr/local/bin/docker-compose /usr/bin/docker-compose
    - sudo chmod 400 -R .ops/ssh/*

# before_script:
#     - my_script

script:
    - .ops/build.sh
    - .ops/push.sh
```


my docker-compose file

```
    web:
        build:
            context: ${GITROOT:-.}
            dockerfile: Dockerfile.web
        image: moovinit_web
        container_name: moovinit_web
        command: npm start
        environment:
            WEB_PORT: ${WEB_PORT:-3200}
            API_URL: ${API_URL:-http://api:3201}
            &lt;&lt;: *node-common
```

Why does it build on my laptop but not on travis?

All Travis Ci Solutions on Gang of Coders

Total of 27 Travis Ci Solutions