Testing/CI/Shippable: Difference between revisions

From QEMU
(Add some more notes)
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''DEPRECATED:''' We have now migrated all our cross-compile tests to the [[Testing/CI/GitLabCI|GitLab CI]] architecture.
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}}


Line 30: Line 32:
= Enabling =
= Enabling =


* Got to shippable.com
* 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

Latest revision as of 11:34, 16 February 2021

DEPRECATED: We have now migrated all our cross-compile tests to the GitLab CI architecture.

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

badge?branch=master&foo=qemu.png [1]

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