GitHub Workflow Pipeline

[TerrenceMcGuinness-NOAA]

Description

Adding a GItHub Workflow for running a global-workflow CI Pipline for checkout-build and running a few test experiments.
A self-hosted "runner" is setup on Orion to run this Pipeline. All interactions with these Pipelines are administered via GitHub such as viewing results and stop and starting the tests.

This version is a "dispatch" mode meaning owners of the GitHub repo can launch the tests with a button on a given branch.
Adding PR based system has been developed and can also update Labels as does the CRON based BASH system.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Clone and Build tests on WCOSS Dell P3
• Cycled test on Orion
• Forecast-only test on Orion

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes need updates to the documentation. I have made corresponding changes to the documentation
• My changes generate no new warnings
• New and existing tests pass with my changes
• Any dependent changes have been merged and published

[WalterKolczynski-NOAA]

Do we even need the labels anymore after this? Won't the tests now appear under "checks" with the rest of the GH actions?

[aerorahul]

Do we even need the labels anymore after this? Won't the tests now appear under "checks" with the rest of the GH actions?

There are nuances to this way of doing CI.
It is not supposed to be permanent in this form.

[aerorahul]

looks great.

[aerorahul]

Here is the resulting pipeline.
Viewable from Github Action itself.