VT-109: factory design patter for build cache manager (f68beec3) · Commits · EBRAINS RI / Tech Hub / Platform / EBRAINS Software Distribution / dedal · GitLab

Skip to content

GitLab

Explore

Sign in

Primary navigation

Project

dedal
- Activity
- Members
- Labels
- Issues
  1
- Issue boards
- Milestones
- Wiki
- Releases
- Harbor Registry

Snippets Groups Projects

f68beec3

Commit f68beec3 authored 1 month ago by

Adrian Ciu

Downloads
- Patches
- Plain Diff

VT-109: factory design patter for build cache manager

parent 81761627

No related branches found

No related tags found

Pipeline #62103 passed with stages

in 38 minutes and 12 seconds

Changes 11
Pipelines 1

Hide whitespace changes

Inline Side-by-side

Showing

dedal/build_cache/BuildCacheManagerCreator.py 41 additions, 0 deletions

dedal/build_cache/BuildCacheManagerCreator.py
dedal/build_cache/BuildCacheManagerOci.py 2 additions, 2 deletions

dedal/build_cache/BuildCacheManagerOci.py
dedal/configuration/SpackConfig.py 4 additions, 1 deletion

dedal/configuration/SpackConfig.py
dedal/enum/SpackCacheStorageEnum.py 25 additions, 0 deletions

dedal/enum/SpackCacheStorageEnum.py
dedal/spack_factory/SpackEnvOperation.py 5 additions, 3 deletions

dedal/spack_factory/SpackEnvOperation.py
dedal/spack_factory/SpackOperation.py 2 additions, 2 deletions

dedal/spack_factory/SpackOperation.py
dedal/spack_factory/SpackOperationCreateCache.py 3 additions, 11 deletions

dedal/spack_factory/SpackOperationCreateCache.py
dedal/spack_factory/SpackOperationUseCache.py 3 additions, 12 deletions

dedal/spack_factory/SpackOperationUseCache.py
dedal/tests/integration_tests/spack_from_scratch_test.py 1 addition, 1 deletion

dedal/tests/integration_tests/spack_from_scratch_test.py
dedal/tests/testing_variables.py 1 addition, 1 deletion

dedal/tests/testing_variables.py
dedal/tests/unit_tests/build_cache_manager_test.py 6 additions, 6 deletions

dedal/tests/unit_tests/build_cache_manager_test.py

with 93 additions and 39 deletions

0% or .

You are about to add 0 people to the discussion. Proceed with caution.

Finish editing this message first!

Please register or sign in to comment