Many CI jobs require Rust and other packages.
The branch ci/ci-base-image publishes to the GitHub Container Registry: https://github.com/frequency-chain/frequency/pkgs/container/frequency%2Fci-base-image
The preference for action usage:
- Official Actions from GitHub (no need to whitelist)
- Actions from Verified Creators (must be pinned to a specific version and whitelisted)
- All other actions (must be thoroughly reviewed, pinned to SHA and whitelisted)
Each GitHub action used in CI must be pinned either to a specific version tag or SHA. The general pinning rules are:
-
The following actions can be pinned to specific version, i.e.
@v1,@v2,@v0.0.1etc. No match strings are allowed.- Official GitHub Actions; OR
- Actions from verified creators displaying "Verified Creator" badge in the GitHub Official Marketplace)
-
All other actions must be pinned to the exact
SHAper GitHub's Using third-party actions guidelines.
Any new external action that is not currently on the approved organization list or a new version of the previously approved action will need to be whitelisted before it can be used in CI.
To whitelist a new action:
For Developers:
- Send a request with the GitHub link to the new action/version you would like to be whitelisted to one of the LibertyDSNP organization owners (currently
@wilwade,@demisx,@sbendar). Please briefly indicate the rationale for your request. - Upon review, the organization owner will respond with either approval or denial of your request. If denied, the organization owner is encouraged to specify the reason for denial and what may be necessary to gain an approval.
For Organization Owners:
Use the Organization Actions Settings page to manage whitelisted actions. If an action cannot be approved, please respond with the reason and any suggestions on how this request may gain your approval. The better effort is made for the requester to understand the denial reason, the less back and forth may be there for you in the future.