-
Notifications
You must be signed in to change notification settings - Fork 171
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduce version file support into develop branch (#1644)
Introduces the use of version files in the `develop` branch. This initial introduction will use version files for runtime only. The ability to force version files for build is included but commented out for now. A follow-up PR will turn on build version forcing when ready. Changes include: 1. Update `module_base.*.lua` modulefiles to use module version variables and remove hardcoded versions. 2. Introduce `build.<platform>.ver`, `run.<platform>.ver` files in the `/versions` folder. 3. Update `sorc/link_workflow.sh` to create `build.ver` and `run.ver` under `/versions` folder based on `build.<platform>.ver` and `run.<platform>.ver`. 4. Introduce sourcing of `run.ver` in `ush/load_fv3gfs_modules.sh` 5. Introduce sourcing of `build.ver` in `sorc/build_all.sh` but commented out for now. Components will continue setting their module versions for the time being. 6. Update `HOMEens_tracker` in `config.vrfy` to use `tracker_ver` from version files. 7. Replace obsproc version in `HOMEobsproc` setting in `parm/config/gfs/config.base.emc.dyn` to use `obsproc_run_ver` from version files. Resolves #671 Resolves #1625
- Loading branch information
1 parent
0004efe
commit 7db6208
Showing
22 changed files
with
483 additions
and
133 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.