These changes are in the Dockerfile, ant build files, and README
We have been using git information in the ant builds, but doing so in a clumsy way: using exec git in the ant build file, which necessitated passing in the whole .git directory in the Dockerfile.
This pull request changes this to instead pass the git information via build arguments. For example:
2. Use a GitHub Action Workflow to create NG-CHM-Artifacts release
These changes are in the .github/workflows directory
Added workflow file NG-CHM-Artifacts_release.yml to address issue #514 .
Additionally, I refactored existing actions (including changing the names of the files) for clarity both in reading the files and viewing the actions in the browser.
This pull request addresses two main concerns:
1. Use build args for git information in Docker
These changes are in the Dockerfile, ant build files, and README
We have been using git information in the ant builds, but doing so in a clumsy way: using
exec git
in the ant build file, which necessitated passing in the whole .git directory in the Dockerfile.This pull request changes this to instead pass the git information via build arguments. For example:
2. Use a GitHub Action Workflow to create NG-CHM-Artifacts release
These changes are in the .github/workflows directory
Added workflow file NG-CHM-Artifacts_release.yml to address issue #514 .
Additionally, I refactored existing actions (including changing the names of the files) for clarity both in reading the files and viewing the actions in the browser.