Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purr-data
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 269
    • Issues 269
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #665

Closed
Open
Opened Jul 30, 2020 by Sam Thursfield@samthursfieldContributor

Use ccache to speed up build times

We can speed up the CI by installing ccache on all of the GitLab CI runners, and using GitLab CI caching to share the $CCACHE_DIR between jobs.

For the Linux runners we can install the ccache package inside the containers. For OSX and Windows the admin of those machines will need to install it in the host.

It's also important that the GitLab CI machines have a reasonable about of disk space dedicated to the CI cache -- at least large enough to fit all the .o files from a build of PD.

Edited Sep 17, 2020 by Sam Thursfield
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: jwilkes/purr-data#665