-
Notifications
You must be signed in to change notification settings - Fork 0
/
azure-pipelines.yml
268 lines (257 loc) · 9.65 KB
/
azure-pipelines.yml
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
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
# Builds hydrologic forecast packages or installer (Debian, Python)
#
trigger:
- main
# - testing
resources:
- repo: self
variables:
tag: '$(Build.BuildId)'
# use pipeline_src_dir to facilitate testing out of Azure Pipeline
pipeline_src_dir: $(Build.SourcesDirectory)
root_out_dir: $(Build.BinariesDirectory)/outputs
# to get a custom '$(Build.BuildNumber)', and 'r' is a counter reset to 1 every change of the major/minor versions
# TODO: reference to this technique on the web?
name: '0.2.$(Rev:r)'
# TODO: test stage, or step if it is worth reusing the ubuntu vm (likely)
stages:
- stage: Build
displayName: Build packages
jobs:
- job: Build
displayName: Build packages
pool:
vmImage: ubuntu-latest
#Cannnot get a service enpoint to work.
#https://github.com/MicrosoftDocs/azure-devops-docs/issues/13741
#container:
# image: sfforecastingctnrregistry.azurecr.io/ubuntu-jammy-202310:20231110
# endpoint: SfFcastDockerSrvConnection
# So, just use dockerhub for now.
container: disparue/ubuntu-jammy-202310:20240517
steps:
- checkout: self
- task: Bash@3
displayName: 'Where are repos checked out'
inputs:
targetType: 'inline'
script: |
echo Build.SourcesDirectory=$(Build.SourcesDirectory)
ls $(Build.SourcesDirectory)
- task: Bash@3
displayName: 'Clone and checkout codebases'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
mkdir -p $(root_out_dir)
chmod go+rw $(root_out_dir)
./checkouts.sh
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Unzip test/doc data'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
echo /usr/local/share/data:
ls /usr/local/share/data
SRC_ROOT=${HOME}/src
sudo ./unzip_testdata.sh ${SRC_ROOT}
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Build and install debian packages'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
chmod +x ./build_debian_pkgs.sh
SRC_ROOT=${HOME}/src
ROOT_BUILD_DIR=${HOME}/build
DEB_PKGS_DIR=$(root_out_dir)/deb_pkgs
mkdir -p ${DEB_PKGS_DIR}
DEB_BUILD_ROOT=${HOME}/debbuild
mkdir -p ${DEB_BUILD_ROOT}
export SUDOCMD=sudo
./build_debian_pkgs.sh ${DEB_PKGS_DIR} ${SRC_ROOT} ${DEB_BUILD_ROOT}
if [ -z "$(ls -A ${DEB_PKGS_DIR})" ]; then
echo "FAILED: package output directory ${DEB_PKGS_DIR} appears to be empty"
exit 1
else
echo "Output in ${DEB_PKGS_DIR}"
ls ${DEB_PKGS_DIR}
fi
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Run C++ unit tests'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
chmod +x ./test_native_libraries.sh
SRC_ROOT=${HOME}/src
./test_native_libraries.sh ${SRC_ROOT} 1
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Build python packages'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
chmod +x ./build_python_pkgs.sh
SRC_ROOT=${HOME}/src
ROOT_BUILD_DIR=${HOME}/build
PY_PKGS_DIR=$(root_out_dir)/py_pkgs
mkdir -p ${PY_PKGS_DIR}
./build_python_pkgs.sh ${PY_PKGS_DIR} ${SRC_ROOT}
if [ -z "$(ls -A ${PY_PKGS_DIR})" ]; then
echo "FAILED: package output directory ${PY_PKGS_DIR} appears to be empty"
exit 1
else
echo "Output in ${PY_PKGS_DIR}"
ls ${PY_PKGS_DIR}
fi
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Build R packages'
inputs:
targetType: 'inline'
script: |
cd $(Build.SourcesDirectory)/packages
chmod +x ./build_r_pkgs.sh
SRC_ROOT=${HOME}/src
ROOT_BUILD_DIR=${HOME}/build
R_PKGS_DIR=$(root_out_dir)/r_pkgs
mkdir -p ${R_PKGS_DIR}
./build_r_pkgs.sh ${R_PKGS_DIR} ${SRC_ROOT}
if [ -z "$(ls -A ${R_PKGS_DIR})" ]; then
echo "FAILED: package output directory ${R_PKGS_DIR} appears to be empty"
exit 1
else
echo "Output in ${R_PKGS_DIR}"
ls ${R_PKGS_DIR}
fi
failOnStderr: false
# Tried `true``, but this seemed to lead to failing tasks without obvious real failure.
# failOnStderr: true
env:
SWIFT_PAT_ENV_VAR: $(SWIFT_PAT) # the recommended way to map to an env variable
BRANCH_NAME_ENV_VAR: $(Build.SourceBranchName)
- task: Bash@3
displayName: 'Code provenance information'
inputs:
targetType: 'inline'
script: |
prov_file=$(root_out_dir)/provenance.md
touch ${prov_file}
SRC_ROOT=${HOME}/src
CSIRO_BITBUCKET=${SRC_ROOT}
cd ${CSIRO_BITBUCKET}/sf-stack
echo "# Source code provenance information" >> ${prov_file}
echo "" >> ${prov_file}
git log -n 1 >> ${prov_file}
failOnStderr: false
- task: Bash@3
displayName: 'Create small artifact with version'
inputs:
targetType: 'inline'
script: |
mkdir -p $(Build.BinariesDirectory)/version
echo $(Build.BuildNumber) > $(Build.BinariesDirectory)/version/version.txt
#- task: Bash@3
# displayName: 'Debug task only, check locations'
# inputs:
# targetType: 'inline'
# script: |
# # Figure out layout of the VM.
# echo pwd:
# pwd
# echo
# ls
# echo $(Pipeline.Workspace)
# ls $(Pipeline.Workspace)
# Note that VSCode may show an intellisense errors for some tasks:
# String does not match the pattern of "^PowerShell@2$"
# This seems to be a bug in VSCode or a plugin. Ignore.
- task: CopyFiles@2
displayName: 'Copy build output to the artifact staging directory'
inputs:
sourceFolder: '$(root_out_dir)'
contents: |
deb_pkgs/**
py_pkgs/**
r_pkgs/**
*.*
targetFolder: '$(Build.ArtifactStagingDirectory)/release'
- task: CopyFiles@2
displayName: Copy files for installer version
inputs:
sourceFolder: '$(Build.BinariesDirectory)/version'
contents: '*.*'
targetFolder: '$(Build.ArtifactStagingDirectory)/version'
- task: Bash@3
displayName: 'Check output with built packages'
inputs:
targetType: 'inline'
script: |
OUT_DIR=$(Build.ArtifactStagingDirectory)/release
if [ -z "$(ls -A ${OUT_DIR})" ]; then
echo "FAILED: package output directory ${OUT_DIR} appears to be empty"
exit 1
fi
cd ${OUT_DIR}
ls -lR
failOnStderr: false
# Note that the MS azure doc seems to advocate using the PublishPipelineArtifact task.
# However this was too abstract to me, without a useful examplar to start from
# Instead, using UniversalPackages which worked out OK
- task: PublishPipelineArtifact@1
inputs:
targetPath: '$(Pipeline.Workspace)'
artifact: 'WaaInstaller'
publishLocation: 'pipeline'
- task: UniversalPackages@0
displayName: Publish output bundle
inputs:
command: publish
publishDirectory: '$(Build.ArtifactStagingDirectory)/release'
vstsFeedPublish: 'OD222236-DigWaterAndLandscapes/hydro_forecast_deb'
vstsFeedPackagePublish: 'swift_deb'
versionOption: custom
versionPublish: '$(Build.BuildNumber)'
packagePublishDescription: 'Debian packages for swift and co.'
- task: UniversalPackages@0
displayName: Publish output bundle version
inputs:
command: publish
publishDirectory: '$(Build.ArtifactStagingDirectory)/version'
vstsFeedPublish: 'OD222236-DigWaterAndLandscapes/hydro_forecast_deb'
vstsFeedPackagePublish: 'swift_deb_version'
versionOption: custom
versionPublish: '$(Build.BuildNumber)'
packagePublishDescription: 'Version number for Debian packages for swift and co. bundle'