Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
229: verify and publish binaries generated by CI r=saem a=alaviss ## Summary This is the final portion of continous delivery pipeline which creates a release based on artifacts created during a CI run done as part of a merge via bors. The release created will contain a JSON manifest and release binaries. The JSON manifest follows this schema: ```json { "manifestVersion": 0, "version": "version identifier (ie. 0.1.0-dev.20000)", "source": { "name": "source-archive-name", "sha256": "checksum" }, "binaries": [ { "target": "the target triplet (eg. x86_64-linux-gnu)", "name": "binary-archive-name", "sha256": "checksum" } ] } ``` This manifest allow tools to easily pick out the artifact that they need depending on the target operating system, and it also prevent the need to hard-code a specific file name format in such tools. ## Details This PR comes with: - A release manifest manipulation tool: This tool is used to create a release manifest from archive manifests generated by niminst. At the moment it does not have many features other than the ones required by the pipeline. Refer to the tool built-in help for details on how to use it. - An additional test in main CI to verify that the release manifest tool can create a release manifest from binaries generated there. - Extra steps in publisher that download and create a release out of artifacts created by main CI. Co-authored-by: Leorize <leorize+oss@disroot.org>
- Loading branch information