travisci missing docs

This repo attempts to document travis-ci.com's quirks to supplement the existing documentation available online.

travisci job build trigger documentation

without merge_mode

https://travis-ci.com/juancarlostong/travisci-docs/builds/110776085

env:
  global:
    var4=4
after_success:
  - echo "af $var4 $var3 $var2 $var1"

result (good):

Setting environment variables from .travis.yml
$ export var4=4
$ bash -c 'echo $BASH_VERSION'
4.3.11(1)-release
0.00s$ echo "s $var1 $var2 $var3 $var4"
s    4
The command "echo "s $var1 $var2 $var3 $var4"" exited with 0.
after_success
0.00s$ echo "af $var4 $var3 $var2 $var1"
af 4

with merge_mode: deep_merge

https://travis-ci.com/juancarlostong/travisci-docs/builds/110777879

merge_mode: deep_merge
env:
  global:
    var4=4
after_success:
  - echo "af $var4 $var3 $var2 $var1"

result (bad):

Setting environment variables from .travis.yml
$ export var4=4
$ bash -c 'echo $BASH_VERSION'
4.3.11(1)-release
0.00s$ echo "s $var1 $var2 $var3 $var4"
s    4
The command "echo "s $var1 $var2 $var3 $var4"" exited with 0.
after_success
0.00s$ echo "af $var4 $var3 $var2 $var1"
af 4
Done. Your build exited with 0.

with merge_mode: deep_merge dont use = sign

https://travis-ci.com/juancarlostong/travisci-docs/builds/110778344

merge_mode: deep_merge
env:
  global:
    var4: 4
after_success:
  - echo "af $var4 $var3 $var2 $var1"

result (good):

Setting environment variables from .travis.yml
$ export var1=1
$ export var2=2
$ export var3=3
$ export var4=4
$ bash -c 'echo $BASH_VERSION'
4.3.11(1)-release
0.00s$ echo "s $var1 $var2 $var3 $var4"
s 1 2 3 4
The command "echo "s $var1 $var2 $var3 $var4"" exited with 0.
after_success
0.00s$ echo "af $var4 $var3 $var2 $var1"
af 4 3 2 1

with merge_mode: deep_merge with changes to after_success

https://travis-ci.com/juancarlostong/travisci-docs/builds/110779451 now that we got deep_merge working, let's see if we can deep merge after_success steps ie. can we run both echo "af $var1 $var2 $var3 $var4" in .travis.yml as well as echo "af $var4 $var3 $var2 $var1" that comes from the build trigger payload?

https://travis-ci.com/juancarlostong/travisci-docs/builds/110779451

merge_mode: deep_merge
env:
  global:
    var4: 4
after_success:
  echo "af $var4 $var3 $var2 $var1"

result (bad):

made no difference from prev run

Setting environment variables from .travis.yml
$ export var1=1
$ export var2=2
$ export var3=3
$ export var4=4
$ bash -c 'echo $BASH_VERSION'
4.3.11(1)-release
0.00s$ echo "s $var1 $var2 $var3 $var4"
s 1 2 3 4
The command "echo "s $var1 $var2 $var3 $var4"" exited with 0.
after_success
0.00s$ echo "af $var4 $var3 $var2 $var1"
af 4 3 2 1

with merge_mode: deep_merge with changes to script

https://travis-ci.com/juancarlostong/travisci-docs/builds/110780013 maybe it only works for script section? ie. can we run both echo "af $var1 $var2 $var3 $var4" in .travis.yml as well as echo "af $var4 $var3 $var2 $var1" that comes from the build trigger payload?

https://travis-ci.com/juancarlostong/travisci-docs/builds/110780013

merge_mode: deep_merge
env:
  global:
    var4: 4
script:
  echo "s $var4 $var3 $var2 $var1"

results (bad):

it looks like we deep_merge only applies to variables and not to sections like script or after_success.

Setting environment variables from .travis.yml
$ export var1=1
$ export var2=2
$ export var3=3
$ export var4=4
$ bash -c 'echo $BASH_VERSION'
4.3.11(1)-release
0.00s$ echo "s $var4 $var3 $var2 $var1"
s 4 3 2 1
The command "echo "s $var4 $var3 $var2 $var1"" exited with 0.
after_success
0.00s$ echo "af $var1 $var2 $var3 $var4"
af 1 2 3 4

artifact uploader documentation

we're trying to flatten the directory structure where files are generated and upload them all into the the root folder of a bucket

atttempt #1 .travis.yml

https://travis-ci.com/juancarlostong/travisci-docs/builds/110787977

addons:
  artifacts: true

script:
  - echo "s $var1 $var2 $var3 $var4" > generated_file_for_uploading.txt

result:

artifacts version v0.7.9-3-geef78ca revision=eef78ca2da49a8783a32d4293c24b7025b52b097
$ export ARTIFACTS_PATHS="$(git ls-files -o | tr \"\\n\" \":\")"
$ artifacts upload
INFO: uploading with settings
  bucket: [secure]
  cache_control: private
  permissions: private
INFO: uploading: /home/travis/build/juancarlostong/travisci-docs/generated_file_for_uploading.txt (size: 9B)
  download_url: https://s3.amazonaws.com/[secure]/juancarlostong/travisci-docs/17/17.1/generated_file_for_uploading.txt
Done uploading artifacts

attempt #2

https://travis-ci.com/juancarlostong/travisci-docs/builds/110790907 download_url: https://s3.amazonaws.com/[secure]/juancarlostong/travisci-docs/17/17.1/generated_file_for_uploading.txt we want to get rid of "juancarlostong/travisci-docs/17/17.1/"

.travis.yml

addons:
  artifacts: true
    target_paths:
      - /

script:
  - echo "s $var1 $var2 $var3 $var4" > generated_file_for_uploading.txt

result (good):

Uploading Artifacts
artifacts.setup
artifacts version v0.7.9-3-geef78ca revision=eef78ca2da49a8783a32d4293c24b7025b52b097
$ export ARTIFACTS_PATHS="$(git ls-files -o | tr \"\\n\" \":\")"
$ artifacts upload
INFO: uploading with settings
  bucket: [secure]
  cache_control: private
  permissions: private
INFO: uploading: /home/travis/build/juancarlostong/travisci-docs/generated_file_for_uploading.txt (size: 9B)
  download_url: https://s3.amazonaws.com/[secure]/generated_file_for_uploading.txt
Done uploading artifacts
Done. Your build exited with 0.

attempt #3

https://travis-ci.com/juancarlostong/travisci-docs/builds/110792995 can we still upload to the bucket's root even if our source file is in some folder structure?

.travis.yml

addons:
  artifacts:
    target_paths:
      - /
    paths:
      - /tmp/upload

script:
  - mkdir -p /tmp/upload
  - echo "s $var1 $var2 $var3 $var4" > /tmp/upload/generated_file_for_uploading.txt
  - echo "s $var1 $var2 $var3 $var4" > dont_want_to_upload_this.txt

result (bad):

no we cant. it'll append "/tmp/upload/" to the destination. at least it didn't upload the random dont_want_to_upload_this.txt file

Uploading Artifacts
artifacts.setup
artifacts version v0.7.9-3-geef78ca revision=eef78ca2da49a8783a32d4293c24b7025b52b097
$ export ARTIFACTS_PATHS="/tmp/upload"
$ artifacts upload
INFO: uploading with settings
  bucket: [secure]
  cache_control: private
  permissions: private
INFO: uploading: /tmp/upload/generated_file_for_uploading.txt (size: 9B)
  download_url: https://s3.amazonaws.com/[secure]/tmp/upload/generated_file_for_uploading.txt
Done uploading artifacts

figure out why bundle install sometimes fails

travis-ci/travis-ci#7499 https://help.rubygems.org/discussions/problems/22609-intermittent-problems-when-pulling-gems check rubygems status: https://status.rubygems.org/history http://www.zhuwu.me/blog/posts/solve-gem-installation-timeout-when-building-docker-image

Gem::RemoteFetcher::UnknownHostError: timed out
(https://rubygems.org/gems/parallel-1.17.0.gem)
An error occurred while installing parallel (1.17.0), and Bundler cannot
continue.

https://github.com/juancarlostong/travisci-docs/blob/66bd3a24405de957769b5e7fec818c17aea4d0b3/.travis.yml

result: able to duplicate error we can see its intermittent nature: https://travis-ci.com/juancarlostong/travisci-docs/builds/110804628

try to fix with newer version of bundler (through using ruby 2.6.0 instead of 2.3.1)

d580c2cbfe3dc47acdcdda67959d1fba37f7cf49

result (good): https://travis-ci.com/juancarlostong/travisci-docs/builds/110805320 docker build doesnt exit anymore because the new bundler version will retry downloading gems.

lower ipv6 priority

according to http://biplane.com.au/blog/?p=122 the reason its failing to download gems is due to ipv6 we try to implement their suggested fix (/etc/gai.conf)

result: no difference

add --full-index to bundle install

rubygems/bundler#2618 (comment)

https://bundler.io/v1.2/bundle_install.html --full-index: Use the rubygems modern index instead of the API endpoint

result (good): https://travis-ci.com/juancarlostong/travisci-docs/builds/110929390