Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !1169

Merged
Created May 11, 2022 by Kirill Smelkov@kirrOwner

golang: Clean internal build cache after part is compiled/tested

  • Overview 5
  • Commits 1
  • Changes 1

@tomo reports that parts/golang1.17/pkg/obj/go-build takes ~ 1GB which makes it wasteful if we want to upload result of compilation to shacache.

It turns out we can drop that particular build cache completely, because it is used only during the build and test of Go itself and its standard library. And when Go is installed it will be another - "user" build cache - that will be used to maintain and reuse build artifacts. For the reference: in SlapOS that latter "user" build cache is located inside go.work/

-> Purge internal build cache after compilation is over.

Size of parts/golang1.17 before and after hereby patch:

before: 1.6G after: 447M

See also related discussion in !929 (comment 128379)

/cc @jerome

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: y/go-clean-own-buildcache
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7