-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pre-Built SIPNET Binary for GitHub Actions #3427
Comments
A couple complications here:
I don't think either of these is a showstopper, just more pieces to put together to get this all working. |
@dlebauer do you mean the sipnet.yml and ci.yml files from the .github/workflows?? |
@asmb123 I am not as familiar with the build system as @infotroph but it may only require editing lines 51-61 in sipnet.yml? |
@infotroph good point about non-permanence and non-public access of artifacts ... I think this motivates creating SIPNET releases where we can make binaries available. |
Until we create SIPNET releases with binaries PecanProject/sipnet#27, here are the binaries that should be accessible to the GH Actions and PEcAn workflow users (e.g.
|
Problem
Currently,
sipnet.yml
inpecanproject/pecan
checks outpecanproject/sipnet
, builds SIPNET from source usingmake
, and then runs PEcAn tests. This adds an unnecessary failure point and compute/time for PEcAn GHAS.Proposed Solution
ci.yml
inpecanproject/sipnet
to build and upload the SIPNET binary as an artifact and updatesipnet.yml
inpecanproject/pecan
to download and use the pre-built binary instead of compiling from source.Benefits
Next Steps
ci.yml
inpecanproject/sipnet
to build and upload SIPNET binary.sipnet.yml
inpecanproject/pecan
to download and use the pre-built SIPNET binary.The text was updated successfully, but these errors were encountered: