Improving travis.yml
See original GitHub issueAs pointed out as a suggestion in #133, we could shorten and improve travis.yml, by moving some instructions into .sh (or .bat) files.
This has already been done for the Linux jobs, see linux.sh. It is executed with
before_install:
- if [ "$TRAVIS_OS_NAME" == "osx" ]; then chmod +x ./.travis/osx.sh; sh ./.travis/osx.sh; fi
We should to that for both osx and windows.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Speeding up the build - Travis CI Docs
Travis CI implements a few optimizations which help to speed up your build ... there is a range of things that can be...
Read more >Customizing the Build - Travis CI Docs
Travis CI uses the .travis.yml file from the branch containing the Git commit that triggers the build. Include branches using a safelist, or...
Read more >Travis CI Tutorial
This is a very short guide to using Travis CI with your cloud platform hosted code repository. If you're new to continuous integration...
Read more >Common Build Problems - Travis CI Docs
My tests broke but were working yesterday #. A very common cause when a test is suddenly breaking without any major code changes...
Read more >Upgrading Travis CI Enterprise 3.x
Before upgrading, we strongly recommend making a backup of PostgreSQL database, Redis and RabbitMQ data. It is recommended that your Travis CI Enterprise ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@naveen521kk instead of saying things like “read this to understand what I mean”, could you please kindly say here exactly what you mean? It’s quite the hassle to have to read half a dozen past comments, and then navigate to another URL in order to understand what you mean. Let’s try to keep the discussion here as self-contained as possible.
This is now obsolete with #196.