Add dev.eessi.io support including project subdirectories#885
Add dev.eessi.io support including project subdirectories#885ocaisa merged 121 commits intoEESSI:2023.06-software.eessi.iofrom
Conversation
Only remove EESSI_DEV_PROJECT
…software-layer into feature/dev.eessi.io-merge2
|
I've finished reworking and testing the I think this is ready for a new review. I tested the changes in this PR using my personal fork of the repository via https://github.com/EESSI/dev.eessi.io-example/pull/. The installations land in the right path: @ocaisa , since you reviewed this before could you take another look and see what you think, please? |
Co-authored-by: ocaisa <alan.ocais@cecam.org>
Co-authored-by: ocaisa <alan.ocais@cecam.org>
These create ${EESSI_PROJECT_INSTALL} and export ${EESSI_DEV_PROJECT}. The first is handled inside the container, the latter must be exported already if this block is running
…-P/software-layer into feature/dev.eessi.io-merge
c9e38e8
into
EESSI:2023.06-software.eessi.io
|
PR merged! Moved |
1 similar comment
|
PR merged! Moved |
|
PR merged! Moved |
This PR replaces open WIP PR #804 (to merge from a more up to date and tested branch) and adds support for building into the
dev.eessi.iorepository.Documentation for how to install into
dev.eessi.iois available in https://www.eessi.io/docs/adding_software/adding_development_software/, with maintainer documentation to come in EESSI/dev.eessi.io-example#12With this PR, software builds are installed into
/cvmfs/dev.eessi.io/2023.06/$EESSI_DEV_PROJECT/.$EESSI_DEV_PROJECTis determined automatically during the build process and comes from the name of the GitHub repository that the bot is listening according to the format:dev.eessi.io-EESSI_DEV_PROJECT. See: https://github.com/EESSI/dev.eessi.io-exampleExisting builds to
dev.eessi.iowere tested with the code that is about to be merged as verified in EESSI/dev.eessi.io-example#14