ornl.ascent CI setup

[andre-merzky]

Note that this PR is based off @zekemorton 's work in the llnl-ci branch and the diff will only be meaningful once that is merged. I'll also squash the commits once that has happened.

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [2725901](https://dashboard.gitguardian.com/incidents/2725901?occurrence=21637104) | MongoDB Credentials | a0e2517bc1a0566ea123765254b14b18d4046d1e | .gitlab-ci.yml | [View secret](https://github.com/ExaWorks/SDK/commit/a0e2517bc1a0566ea123765254b14b18d4046d1e#diff-037ea159eb0a7cb0ac23b851e66bee30fb838ee8d0d99fa331a1ba65283d37f7R41) | | [2725901](https://dashboard.gitguardian.com/incidents/2725901?occurrence=21653531) | MongoDB Credentials | 3043915a8999edf8f6a579ac75250193854848af | .gitlab-ci.yml | [View secret](https://github.com/ExaWorks/SDK/commit/3043915a8999edf8f6a579ac75250193854848af#diff-037ea159eb0a7cb0ac23b851e66bee30fb838ee8d0d99fa331a1ba65283d37f7L41) | | [2726525](https://dashboard.gitguardian.com/incidents/2726525?occurrence=21653532) | MongoDB Credentials | bf992860a53e97259cad9dfe013a49d1211d38eb | ci/tests/rp/test.sh | [View secret](https://github.com/ExaWorks/SDK/commit/bf992860a53e97259cad9dfe013a49d1211d38eb#diff-b2143118b11ea9eb118a52785f1a86030f739ab04e2d72fc6a2aa4ff74770519R3) | | [2726525](https://dashboard.gitguardian.com/incidents/2726525?occurrence=21660901) | MongoDB Credentials | 74275845e3f1b2ee8d281728480c33a7fb622937 | ci/tests/rp/test.sh | [View secret](https://github.com/ExaWorks/SDK/commit/74275845e3f1b2ee8d281728480c33a7fb622937#diff-b2143118b11ea9eb118a52785f1a86030f739ab04e2d72fc6a2aa4ff74770519L3) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secrets safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate these secrets](https://docs.gitguardian.com/secrets-detection/detectors/specifics/mongo_uri#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/internal-repositories-monitoring/integrations/git_hooks/pre_commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[zekemorton]

This looks great! Just a few discussion points so that we can keep the two pipelines consistent with each other!

It looks like the conda/rockylinux builds are now failing during flux portion of the install process, do we want to remove that combination from the build matrix for now and create a ticket to investigate further?

[andre-merzky]

Hi @zekemorton : I merged the changes from the llnl-ci branch and things look ok. This should best be reviewed though after llnl-ci is merged though to reduce the diff footprint.

[andre-merzky]

It looks like the conda/rockylinux builds are now failing during flux portion of the install process, do we want to remove that combination from the build matrix for now and create a ticket to investigate further?

Yes, that might be the best way forward right now.

GH tests are also complaining about the MongoDB credential I added to the script (and rightly so), so I will have to clean that up also.

[andre-merzky]

It looks like the conda/rockylinux builds are now failing during flux portion of the install process, do we want to remove that combination from the build matrix for now and create a ticket to investigate further?

Yes, that might be the best way forward right now.

So what fails is the centos7 / pip / mpich / python-3.7 combination. I would be inclined to disable python-3.7 for now, as would have the smallest impact on the other tests (I think?) - or do you see a way to disable that specific combination?

[andre-merzky]

.

So what fails is the centos7 / pip / mpich / python-3.7 combination. I would be inclined to disable python-3.7 for now, as would have the smallest impact on the other tests (I think?) - or do you see a way to disable that specific combination?

@wilke, @mtitov : never mind that part - the test which previously failed seems to work now ¯\_(ツ)_/¯

[andre-merzky]

I seem to remember that we wanted to disable that rockylinux8 configuration because of the Flux build failure - so merging this anyway...