Add CIs to release new version and publish binary files (#1648)

Add CIs to enable the release process of a new version of WAMR,
and build and publish the binary files when a version is released,
including iwasm, wamrc, lldb, vscode-extension and wamr-ide for
Ubuntu-20.04, Ubuntu-22.04 and MacOS.

And refine the CIs to test spec cases.
This commit is contained in:
Wenyong Huang
2022-10-28 13:55:41 +08:00
committed by GitHub
parent 77ff7daaf4
commit 84161fe084
28 changed files with 1936 additions and 608 deletions

View File

@ -37,7 +37,26 @@ under `resource/debug/bin`.
- Ubuntu Bionic 18.04(LTS)
```
#### 3. Build docker images
#### 3. Pull docker images from the registry(recommended) or build docker images on the host
##### 3.1 Pull docker images from registry
From now on, for each release, we have the same version tagged docker image pushed to GitHub package.
You could simply pull a certain version of docker images using the following commands:
```sh
# pull and retag wasm-toolchain
docker pull ghcr.io/bytecodealliance/wasm-toolchain:{version number}
docker tag ghcr.io/bytecodealliance/wasm-toolchain:{version number} wasm-toolchain:{version number}
docker rmi ghcr.io/bytecodealliance/wasm-toolchain:{version number}
# pull and retag wasm-debug-server
docker pull ghcr.io/bytecodealliance/wasm-debug-server:{version number}
docker tag ghcr.io/bytecodealliance/wasm-debug-server:{version number} wasm-debug-server:{version number}
docker rmi ghcr.io/bytecodealliance/wasm-debug-server:{version number}
```
##### 3.2 Build docker images on host
We have 2 docker images which should be built or loaded on your host, `wasm-toolchain` and `wasm-debug-server`. To build these 2 images, please enter the `WASM-Debug-Server/Docker` & `WASM-Toolchain/Docker`, then execute the `build_docker_image` script respectively.