-
Task
-
Resolution: Done
-
Major
-
2.13.0.GA
-
False
-
False
-
In order to effectively distribute sources of CRW, as well as make builds more reproducible, CRW should adopt Cachito. Usage of Cachito with our build system is described in detail here:
Additional helpful info can be found in the package-managers section of the upstream project:
Essentially you specify the top level projects you're pulling in for your image, and with proper dependency declarations, cachito will crawl through the tree and gather all of them, and make them available to your builds. This enables our internal tooling to distribute those sources later.
In order to enable source containers, this should be enabled for all supported streams.
Related issues: CRW-2370, CRW-2371
Applicable to npm, pip, gomod, yarn
- https://source.redhat.com/groups/public/container-build-system/container_build_system_wiki/containers_from_source_multistage_builds_in_osbs#jive_content_id_Cachito_Integration_for_npm
- https://source.redhat.com/groups/public/container-build-system/container_build_system_wiki/containers_from_source_multistage_builds_in_osbs#jive_content_id_Cachito_Integration_for_pip
- https://source.redhat.com/groups/public/container-build-system/container_build_system_wiki/containers_from_source_multistage_builds_in_osbs#jive_content_id_Cachito_Integration_for_gomod
- https://source.redhat.com/groups/public/container-build-system/container_build_system_wiki/containers_from_source_multistage_builds_in_osbs#jive_content_id_Cachito_Integration_for_yarn
- is duplicated by
-
CRW-2379 Could cachito be used for pip, npm, golang vendoring?
- Closed
- is related to
-
CRW-360 Use internal npm registry for CRW builds / switch to cachito
- Closed
- relates to
-
CRW-2619 udi: python :: remove old lang server; switch to flake8 linter; verify pytest, venv & pip work in che-code editor
- Resolved