Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🛠️ [TASK] : Unify our builders into one master builder. #322

Open
8 tasks
stevenj opened this issue Oct 1, 2024 · 0 comments
Open
8 tasks

🛠️ [TASK] : Unify our builders into one master builder. #322

stevenj opened this issue Oct 1, 2024 · 0 comments
Assignees

Comments

@stevenj
Copy link
Collaborator

stevenj commented Oct 1, 2024

Summary

Simplify Builder setup and improve caching.

Description

We have many builders, and they are often redundant.
So, it makes sense to unify them into one, that contains all our tools.
We also use versioned containers from external sources, maintaining those across multiple repos is problematic, we should make our own version of those containers, so there is a single version to update, and when we update the cat-ci version, everything gets the latest tagged versions.

  • Create a new earthly sub-directory that contains ROOT Containers.

    • Create a master "builder" target.
      • it should be based on debian slim, and should 'apt-get install' all the common tooling we always use. OpenSSL, wget, curl, graphviz, etc, etc.
      • It should have then a list of DO +ADD_FLUTTER_TOOLS and DO +ADD_PYTHON_TOOLS, DO +ADD_GOLANG_TOOLS, DO +ADD_RUST_TOOLS etc.
      • The individual languages then, do not have an actual builder, they define a ADD_<LANGUAGE>_TOOLS which does the specific set of steps required to add tools for that language.
      • If Chrome/Firefox etc, are generic, they could have their own ADD_BROWSER_TOOLS targets, etc.
  • We should have generic containers, which point to upstream versioned containers. There should be no direct references in any repo to an external container in a FROM <something> line inside earthly.

  • Fix the documents

@bkioshn bkioshn self-assigned this Oct 1, 2024
@bkioshn bkioshn moved this from New to 🔖 Ready in Catalyst Oct 1, 2024
@bkioshn bkioshn moved this from 🔖 Ready to 🏗 In progress in Catalyst Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🔖 Ready
Development

No branches or pull requests

2 participants