Skip to content

optimize building recipes #42

Description

@mahf708

We could utilize preexiting spack cache instead of rebuidling every little thing. Building cmake alone is a total monster of a job. :)

Example of how to do it, but there are others, and this could easily be an issue for claudio

# TODO: do these intervene with each other?
# https://cache.spack.io/tag/v0.23.0/
RUN spack mirror add v0.23.0 https://binaries.spack.io/v0.23.0
RUN spack buildcache keys --install --trust
# https://cache.spack.io/tag/v0.23.0/?stack=e4s
RUN spack mirror add v0.23.0-e4s https://binaries.spack.io/v0.23.0/e4s
RUN spack buildcache keys --install --trust
# https://cache.spack.io/tag/v0.23.0/?stack=root#
RUN spack mirror add v0.23.0-root https://binaries.spack.io/v0.23.0/root
RUN spack buildcache keys --install --trust
# TODO: add e4s inventory when they support ubuntu 22.04+
# # https://oaciss.uoregon.edu/e4s/inventory.html
# RUN spack mirror add E4S-24.0 https://cache.e4s.io/24.0
# RUN spack buildcache keys -it
# RUN spack mirror add E4S https://cache.e4s.io
# RUN spack buildcache keys -it

cc @bartgol

Originally posted by @mahf708 in #40 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions