is-ci | Detect if the current environment is a CI server | Continous Integration library

Resolved this, set it up differently though. See below. I think the stages have to be set up with the jobs/include object as seen below

see new travis.yml

Here is documentation for how to add a workflow status badge.

The status badge represents an image - .png this image is automatically updated by GitHub - e.g if your workflow is:

• successful the badge will be "green" and the status "success"
• failing the badge will be "red" and the status "failed"

The first part of the badge is the name of the workflow (either the name: attribute or the name of the file)

You can also use the UI to generate a badge. See more in this answer.

Q: Do I need to have the badge in my readme before I run the action?

A: No you can add it anytime, if you add it before the workflow it shows no information (gray coloring). Keep in mind that you may need to "force refresh" the browser to see the new image (browser caching images)

Q: Is the build badge a stable url, or is it changed by the action at runtime?

A: It is as stable as the name of the workflow - if you change the name the badge will stop working.

Q: Is this something you can even do with actions or do you need to use travis-ci?

A: It is GitHub Action functionality, you do not need Travis-CI

The problem was being caused by an issue with illegal reflective operations and the Kotlin Maven Plugin with any project over Java 9 (my project uses Java 15). As described by this thread on YouTrack, a workaround is to:

A workaround is to run mvn with the following environment variable: MAVEN_OPTS=--illegal-access=permit

Adding a global environment variable with the same value to my .travis.yml fixed the issue.

You need Java 11 to build the project. I was able to build it locally using JDK 11. I used maven wrapper. You can try using the following command.

Per the docs there are three methods:

• Using the UI: "More options" -> "Caches" on the repo's page
• Using the CLI: travis cache --delete
• Using the API: DELETE /repos/{repository.id}/caches

That said, Docker images are one of the examples explicitly called out as a thing not to cache:

Large files that are quick to install but slow to download do not benefit from caching, as they take as long to download from the cache as from the original source

In your example it's not clear what's involved in the pipeline beyond that Dockerfile - even if the file itself hasn't changed, any of the things that go into it (base image, source code, etc.) might have. Caching the image means you may get false positives, builds that pass even though docker build would have failed.

I fixed it.

GitHub has Jekyll running behind it which will mess up special paths (here the underscore paths). You can disable jekyll by just creating a .nojekyll file in the root directory of the branch. If you use travis-CI for something like that and run a tox script just call the command touch {toxinidir}/.nojekyll

This will result in a working website for me.

After some search, here is what I got:

The most convenient way seems to deploy the generated files to GitHub pages. The process is explained here: https://docs.travis-ci.com/user/deployment/pages/. In short:

• first, create a GitHub page from the repository under test. This can be done through the Github web of the repository. The outcome includes an additional remote branch called gh-=pages generated.

• then, in .travis.yml, use the deploy section to specify the condition to do the deployment.

I got an answer after some search, which also corresponds to the comments above.

By default, all files in the home directory of the travis ci server (including subdirectores) will be uploaded to GitHub pages. If local_dir is specified in the "deploy" section of travis ci, then only files in local_dir will be uploaded.

The issue is that the build is being execute two times based on the mvn install followed by mvn package which is defined in travis.yml file. This causes the issue.