-
Notifications
You must be signed in to change notification settings - Fork 0
110 lines (85 loc) · 3.4 KB
/
Copy pathrelease.yml
File metadata and controls
110 lines (85 loc) · 3.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on:
push:
# Sequence of patterns matched against refs/tags
tags:
- 'v*' # Push events to matching v*, i.e. v1.0, v20.15.10
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
build:
# The type of runner that the job will run on
runs-on: windows-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
- name: Extract tag name
id: tag
uses: actions/github-script@0.2.0
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
script: |
return context.payload.ref.replace(/\/refs\/tags\//, '');
- name: Echo tag
run: echo ${{ steps.tag.outputs.result }}
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
with:
submodules: 'recursive'
- name: update submodules' tags
run: git submodule foreach --recursive 'git fetch --tags'
- uses: microsoft/setup-msbuild@v1.0.0
with:
vs-version: 16.5
- uses: actions/setup-dotnet@v1
with:
dotnet-version: '3.1.x' # SDK Version to use; x will use the latest version of the 3.1 channel
- uses: actions/setup-python@v2
with:
python-version: '3.x' # Version range or exact version of a Python version to use, using SemVer's version range syntax
- name: Bootstrap
run: python bootstrap.py
timeout-minutes: 3
- name: Prepare Release
run: python prepare_release.py ${{ steps.tag.outputs.result }}
- name: Restore using netcore
run: dotnet restore
timeout-minutes: 5
- name: Build Release
run: MsBuild TDiffBackup.sln /t:Build /p:Configuration=Release
timeout-minutes: 5
- name: Test using netcore
run: dotnet test --configuration Release
timeout-minutes: 5
- name: Install python deps
run: python -m pip install --user requests bsdiff4
timeout-minutes: 5
- name: Run integration python test script
run: python tests.py
timeout-minutes: 20
- uses: actions/upload-artifact@v2
with:
name: Release Build
path: DiffBackup/bin/Release/DiffBackup.*
- name: Create Release
id: create_release
uses: actions/create-release@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
tag_name: ${{ github.ref }}
release_name: Release ${{ github.ref }}
draft: true
prerelease: false
- name: Upload Release Asset
id: upload-release-asset
uses: actions/upload-release-asset@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
asset_path: ./DiffBackup/bin/Release/DiffBackup.dll
asset_name: DiffBackup.dll
asset_content_type: "application/octet-stream"