Welcome
The Unified Forecast System (UFS) development process relies on continuous integration and deployment (CI/CD) pipelines to ensure software reliability and performance across platforms. These pipelines run automatically upon code updates and generate build artifacts tested on a variety of NOAA-affiliated High-Performance Computing (HPC) systems. Artifact results are available for UFS applications including the Short-Range Weather (SRW) App, UFS Weather Model, and Land DA Workflow.
Description
This page summarizes recent CI/CD builds for key UFS repositories. The artifacts correspond to pull request builds executed on multiple HPC systems such as Hera, Orion, Derecho, Jet, and Gaea, using various compiler environments (e.g., Intel, GNU). Each build includes validation metrics, SonarQube analysis results, and run durations.
All builds are marked as either Success, Failure, Aborted, or Not Built and include Jenkins artifact .csv and json artifact generation.
Getting Started
These CI/CD pipelines run automatically when changes are proposed via GitHub pull requests. Each build confirms compatibility across NOAA’s major computing environments and produces artifacts accessible through internal developer tools.
Developers and collaborators are encouraged to use these results to ensure cross-platform consistency and to validate new features. SonarQube results are also integrated into each build for static code quality analysis.
For more information on how to contribute to these applications or use the artifacts, please refer to the corresponding UFS application documentation and user guides.
Explanation of Data
The pull request number and build number for the pipeline run, shown as “PR-<pull-request> #<build-number>”
The current status of the build, either finished if complete or in progress if still running.
The total time the build took to run on Jenkins, measured in minutes.
The start date and time of the build recorded in Zulu (UTC) time.
The outcome of the build for each supported platform and SonarQube scan, showing success, failure, aborted, or not built.
Logs and output files generated from the build that can be downloaded without direct Jenkins access.
