Skip to content

Reduce the travis build time #9387

@lannka

Description

@lannka

Right now it takes travis ~30m for a pull request and ~40m for a release build. Let's speeeed it up!!

gulp.js lint. Total time: 0m 51s.
gulp.js check-types. Total time: 0m 47s.
gulp.js presubmit. Total time: 0m 25s.
gulp.js dep-check. Total time: 1m 46s.
gulp.js build. Total time: 2m 10s.
gulp.js dist --fortesting. Total time: 12m 22s.
gulp.js test --nobuild --compiled. Total time: 7m 33s.
gulp.js test --nobuild --saucelabs --integration --compiled. Total time: 7m 25s.
cd validator && python build.py. Total time: 1m 58s.
cd validator/webui && python build.py. Total time: 0m 16s.

Some ideas:

  • Parallelize jobs on different VMs. All presubmit checks can be moved to a separate VM (~4min). Validator checks too (~2m).
  • skip gulp build (2m 10s), since we only test against gulp dist (caveat: we might need gulp build --css-only to get gulp dist running, or we should fix the deps)
  • saucelabs tests do not consume local CPU, can be definitely parallelized. (7m 25s)
  • Optimize our compiler, build all extensions in one shot (12m) (@cramforce is it still possible?)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions