Problem: subsequent framework projects will need to link against flux-core and its associated libraries. These projects (such as flux-pmix, flux-sched, and flux-coral2) are needed on various LC systems for testing flux with our LC flavors of MPI.
Adapt the flux-core build to build in a shared workspace directory unique to each pipeline (set of GitLab CI jobs) and cluster. Break the core build and test into separate steps for speed. Build and install subsequent framework projects in the same shared directory, which will persist after the tests.
Problem: subsequent framework projects will need to link against flux-core and its associated libraries. These projects (such as flux-pmix, flux-sched, and flux-coral2) are needed on various LC systems for testing flux with our LC flavors of MPI.
Adapt the flux-core build to build in a shared workspace directory unique to each pipeline (set of GitLab CI jobs) and cluster. Break the core build and test into separate steps for speed. Build and install subsequent framework projects in the same shared directory, which will persist after the tests.
Here's a visual example of what this looks like: