Testing/CI/Shippable: Difference between revisions
(Add some more notes) |
|||
| Line 30: | Line 30: | ||
= Enabling = | = Enabling = | ||
* | * Go to shippable.com | ||
* Login with GitHub | * Login with GitHub | ||
* Shippable should automatically enable runs when you push to a github repo with .shippable enabled | * Shippable should automatically enable runs when you push to a github repo with .shippable enabled | ||
Revision as of 11:33, 16 February 2021
Shippable is used mostly to do our cross compile testing. It uses the existing docker infrastructure to build out major architectures. The configuration is in .shippable.yml
Configuration
Tests are controlled via .shippable.yml
Targets
Currently we cross compile for:
- win32/win64
- 32 bit ARM (armel/armhf)
- 64 bit ARM (aarch64)
- s390x
- 32 bit MIPS (mips)
- 64 bit MIPS (mips64el)
- 64 bit Power (ppc64el)
Current Status
Common Failures
The two most common failure modes are:
- 32/64 bit compile failure, usually because the developer only built on 64 bit
- failure to build the docker image due to network stability
Enabling
- Go to shippable.com
- Login with GitHub
- Shippable should automatically enable runs when you push to a github repo with .shippable enabled