Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 362
    • Issues 362
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #668

Closed
Open
Created Aug 11, 2020 by Sam Thursfield@samthursfieldContributor

ci: Cache downloaded nw.js tarball

We can persist files between builds in the /cache folder, provided it's enabled in the .gitlab-ci.yml config. (Details at https://docs.gitlab.com/ee/ci/caching/)

For the CI script to do this, it needs to know the nw.js filename for the current platform. This info is currently determined in the tar_em_up.sh script. I propose that we move that code into a separate nwjs_version_for_platform shell script which we could then call both from tar_em_up.sh and from .gitlab-ci.yml.

Edited Aug 11, 2020 by Sam Thursfield
Assignee
Assign to
Time tracking