KhronosGroup / KhronosGroup/COLLADA2GLTF

Consider options for CI speed-up

Open
#189 1 comment 0 reactions 0 assignees View on GitHub
build discussion enhancement
Dominant language
C++
Stars
573
Forks
154
PR merge metrics
No merged PRs in 30d

Description

On building with Docker:

I'm only familiar with this on GitLab CI and don't know the details of how Travis and Appveyor handle this, so take it with a grain of salt.

When you do docker builds in GitLab CI it effectively caches the state of the project as a container snapshot. That way when you make a change, it just pulls in the delta and likewise CMake + make will only have to rebuild the delta which can save a lot of time on builds in CI.

Generally this works well, so if it's possible to do something similar in Travis and Appveyor it will help build times in a much friendlier way than the current approach of downloading pre-compiled libs from older builds.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the Travis and Appveyor CI configuration and the current process for downloading pre-compiled libraries. Compare whether Docker-layer or project-state caching can preserve incremental CMake and make builds in both services. Done means a documented, tested caching approach that improves CI build times without relying on older pre-compiled libraries.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, docker
Domain
build-system, ci-cd, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.