Gatsby: Investigate CI optimisation

Created on 18 Jul 2018 · 5Comments · Source: gatsbyjs/gatsby

Summary

Gatsby runs a lot of CI builds every day. Spend some time to see if they can be sped up.

Basic example

Things to investigate:

caching between runs?
run jobs in parallel?
remove unnecessary work? e.g. use npx?
review / reduce dependencies?

Windows CI builds are particularly slow. How can they be sped up?

use a paid Appveyor account?
use Visual Studio Team Services CI instead?

Motivation

Spend less time waiting for CI builds to finish.

stale? maintenance

Source

m-allanson

👍3

All 5 comments

You might want to check out other free CI services. SemaphoreCI might be a good choice, they recently doubled their capacity for open-source projects and are blazing fast.

mmaksimovic on 18 Jul 2018

👍1

That looks promising! You want to try running our tests on their service (e.g. fork the repo and setup your fork to run there) and see how the test times compare?

KyleAMathews on 18 Jul 2018

👍1

Hey @m-allanson and @KyleAMathews

Here are my results on Semaphore and here are the latest results on Travis. I'll add my results from Travis later on, since the build is waiting in queue for quite a long time.

Hope I helped :)

mmaksimovic on 25 Jul 2018

👍1

Old issues will be closed after 30 days of inactivity. This issue has been quiet for 20 days and is being marked as stale. Reply here or add the label "not stale" to keep this issue open!