This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Why do we build using go build -a
and have removed buildkit caching?
#2730
Labels
Bug description
It currently takes an hour to build tanzu framework to any reasonable state on a Ryzen 5900X with 64GB RAM.
Is there a particular reason to use
go build -a
when the golang compiler does reproducible builds when not using cgo?Also, it seems we used to use buildkit caching going by some of the comments in the Dockerfiles, but that this was removed. Is there a reason for doing so?
Expected behavior
Builds take a lot less than 1 hour.
Steps to reproduce the bug
Version (include the SHA if the version is not obvious)
Environment where the bug was observed (cloud, OS, etc)
Relevant Debug Output (Logs, manifests, etc)
The text was updated successfully, but these errors were encountered: