Fer*_*nez 16 continuous-integration android github github-release github-actions
因此,我尝试在 yml 文件上为生成的工件实现发布部分,并解释自己:我想使用 yml 文件将工件添加到我的版本中。
这是我正在为 Android 应用程序处理的唯一 yml 文件:
name: Android CI
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- run: mkdir -p app/build/outputs/apk/release
- run: echo hello > app/build/outputs/apk/release/app-release-unsigned.apk
- uses: actions/upload-artifact@v2
with:
name: my-artifact
path: app/build/outputs/apk/release/app-release-unsigned.apk
- name: set up JDK 1.8
uses: actions/setup-java@v1
with:
java-version: 1.8
- name: Permition Gradlew
run: chmod +x gradlew
- name: Build Gradlew
run: ./gradlew assembleRelease
Run Code Online (Sandbox Code Playgroud)
该actions/upload-artifact@v2操作用于将工件上传到 GitHub Actions 工作流程运行,而不是用于将资产添加到 GitHub 版本。如果您想将构建资产添加到 GitHub 版本,则应该使用此处softprops/action-gh-release描述的示例。我修改了示例以匹配您的具体场景:
on:
push:
# Sequence of patterns matched against refs/tags
tags:
- 'v*' # Push events to matching v*, i.e. v1.0, v20.15.10
name: Upload Release Asset
jobs:
build:
name: Upload Release Asset
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Build project
run: |
mkdir -p app/build/outputs/apk/release
echo hello > app/build/outputs/apk/release/app-release-unsigned.apk
- name: Release with Notes
uses: softprops/action-gh-release@v1
with:
files: |
app/build/outputs/apk/release/app-release-unsigned.apk
other/files/as/needed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Run Code Online (Sandbox Code Playgroud)
您可以根据需要使用不同的路径重复最后一步,以将更多工件添加到版本中。
| 归档时间: |
|
| 查看次数: |
11106 次 |
| 最近记录: |