Testing/CI/Shippable: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Shippable is used mostly to do our cross compile testing. It uses the existing [[Testing/DockerBuild|docker]] infrastructure to build out major architectures. The configuration is in {{src|path=.shippable.yml}} | Shippable is used mostly to do our cross compile testing. It uses the existing [[Testing/DockerBuild|docker]] infrastructure to build out major architectures. The configuration is in {{src|path=.shippable.yml}} | ||
= Current Status = | |||
{{{ShippableCIStatus}}} | |||
= Targets = | |||
Currently we cross compile for: | |||
* 32 bit ARM (armel/armhf) | |||
* 64 bit ARM (aarch64) | |||
* s390x | |||
* 32 bit MIPS (mips) | |||
* 64 bit MIPS (mips64el) | |||
* 64 bit Power (ppc64el) | |||
= Failures = | = Failures = |
Revision as of 12:07, 20 May 2019
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
Current Status
{{{ShippableCIStatus}}}
Targets
Currently we cross compile for:
- 32 bit ARM (armel/armhf)
- 64 bit ARM (aarch64)
- s390x
- 32 bit MIPS (mips)
- 64 bit MIPS (mips64el)
- 64 bit Power (ppc64el)
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