This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathops.deploy.props
545 lines (502 loc) · 19 KB
/
ops.deploy.props
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
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
<?xml version="1.0" encoding="utf-8"?>
<Project
DefaultTargets="Run"
ToolsVersion="14.0"
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!--
**** PREPARE - CALCULATE HASHES ****
-->
<!--
The collection of files for which the hashes need to be calculated. The available hash algorithms
are:
- MD5
- SHA1
- SHA256
- SHA512
Hash values are stored in a file in the temp directory and can be retrieved with the
'ReadHashFromFile' task
-->
<ItemGroup Condition=" '$(ShouldLoadFilesToHash)' == 'true' ">
<!-->
<FilesToHash Include="">
<Algorithm></Algorithm>
</FilesToHash>
-->
</ItemGroup>
<!--
**** PREPARE - COPY FILES ****
-->
<!--
Files that should be copied, either from the file system or from a NuGet package.
-->
<ItemGroup Condition=" '$(ShouldLoadFilesToCopy)' == 'true' ">
<!--
<FilesToCopy Include="">
<Destination></Destination>
</FilesToCopy>
-->
</ItemGroup>
<ItemGroup Condition=" '$(ShouldLoadNuGetFilesToCopy)' == 'true' ">
<!--
<NuGetFilesToCopy Include="My.Cool.NuGet.Package">
<Include>**/*.*</Include>
<Destinations>$(DirBuildTemp)</Destinations>
</NuGetFilesToCopy>
-->
</ItemGroup>
<ItemGroup Condition=" '$(ShouldLoadArchiveFilesToCopy)' == 'true' ">
<!--
<ArchiveFilesToCopy Include="">
<Destination></Destination>
</ArchiveFilesToCopy>
-->
</ItemGroup>
<!--
**** PUSHTO - DIRECTORY / FILESERVER ****
-->
<!--
The ItemGroup defining the files that should be pushed to a given deployment directory.
The IncludedFiles and the ExcludedFiles are lists of files that
should be included (or excluded) in the list of files to deploy. Each entry is separated by a semi-colon(;).
The PushToDirectorySpecs, IncludedFiles and ExcludedFiles all allow the insertion of build templates,
e.g. \\MyServer\${ProductNameInFilePath}\${VersionSemantic}
-->
<ItemGroup Condition=" '$(ShouldLoadPushToDirectorySpecs)' == 'true' ">
<!--<PushToDirectorySpecs Include="\\MyServer\${ProductNameInFilePath}\${VersionSemantic}">
<IncludedFiles>
$(DirBuildDeploy)\myfile.zip
</IncludedFiles>
<ExcludedFiles>
</ExcludedFiles>
</PushToDirectorySpecs>-->
</ItemGroup>
<!--
**** PUSHTO - NUGET ****
-->
<PropertyGroup>
<!--
The URL to which all NuGet packages should be pushed. By default it pushes to nuget.org.
If the repository needs authentication then the API key should be defined via an environment variable:
NuGetApiKey - The NuGet API key for the NuGet feed
-->
<!--<NuGetSourceUrl>UNDEFINED</NuGetSourceUrl>-->
</PropertyGroup>
<!--
The ItemGroup defining which packages should be pushed up to the NuGet package source.
Allows build templates, e.g. $(DirBuildDeploy)\${VersionSemantic}\*.nupkg.
-->
<ItemGroup Condition=" '$(ShouldLoadNuGetPackagesToPush)' == 'true' ">
<!--
<NuGetPackagesToPush
Condition=" '$(DirBuildDeploy)' != '' "
Include="$(DirBuildDeploy)\*.nupkg"
Exclude="$(DirBuildDeploy)\*.symbols.nupkg" />
-->
</ItemGroup>
<!--
**** PUSHTO - SYMBOL SERVER ****
-->
<!--
The ItemGroup defining which symbol packages should be pushed up to the symbol server.
Allows build templates, e.g. $(DirBuildDeploy)\${VersionSemantic}\*.symbols.nupkg.
-->
<PropertyGroup>
<!--
The URL to which all NuGet symbol packages should be pushed. If the repository needs authentication then
the API key should be defined via an environment variable:
NuGetApiKey - The NuGet API key for the NuGet feed
-->
<!--<NuGetSymbolSourceUrl>UNDEFINED</NuGetSymbolSourceUrl>-->
<!--
The URL / UNC path to which all the symbol packages should be pushed.
-->
<!--<SymbolServerUncPath>UNDEFINED</SymbolServerUncPath>-->
</PropertyGroup>
<ItemGroup Condition=" '$(ShouldLoadSymbolPackagesToPush)' == 'true' ">
<!--
<SymbolPackagesToPush
Condition=" '$(DirBuildDeploy)' != '' "
Include="$(DirBuildDeploy)\*.symbols.nupkg" />
-->
</ItemGroup>
<!--
**** PUSHTO - GITHUB RELEASE ****
-->
<!--
The ItemGroup defining the files that should be pushed to a GitHub release. All properties
except for the Repository allow the use of build templates, e.g. $(DirBuildDeploy)\myarchive-${VersionSemantic}.zip
-->
<ItemGroup Condition=" '$(ShouldLoadPushToGitHubReleaseSpecs)' == 'true' ">
<!--
<PushToGitHubReleaseSpecs Include="${VersionSemantic} - My release">
<Repository>MyCoolProject</Repository>
<Description>${ReleaseNotes}</Description>
<IncludedFiles>
$(DirBuildDeploy)\myarchive-${VersionSemantic}.zip
</IncludedFiles>
<ExcludedFiles>
</ExcludedFiles>
</PushToGitHubReleaseSpecs>
-->
</ItemGroup>
<!--
**** PUSHTO - GIT BRANCH ****
-->
<!--
The ItemGroup defining the files that should be pushed to a GIT branch. All properties
allow the use of build templates, e.g. $(DirBuildDeploy)\myarchive-${VersionSemantic}.zip
-->
<ItemGroup Condition=" '$(ShouldLoadPushToGitBranchSpecs)' == 'true' ">
<!--
<PushToGitBranchSpecs
Condition=" '$(DirBuildDeploy)' != '' "
Include="$(DirBuildDeploy)\myarchive-${VersionSemantic}.zip">
<Repository>$(GitRemoteRepository)</Repository>
<Branch>master</Branch>
<ExtractZipFiles>true</ExtractZipFiles>
<CommitMessage>New changes</CommitMessage>
</PushToGitBranchSpecs>
-->
</ItemGroup>
<!--
**** PUSHTO - GIT REPOSITORY ****
-->
<!--
The ItemGroup defining the zip files containing a git workspace that should be pushed to a GIT repository.
All properties allow the use of build templates, e.g. $(DirBuildDeploy)\myarchive-${VersionSemantic}.zip
-->
<ItemGroup Condition=" '$(ShouldLoadPushToGitRepositorySpecs)' == 'true' ">
<!--
<PushToGitRepositorySpecs
Condition=" '$(DirBuildDeploy)' != '' "
Include="$(DirBuildDeploy)\myarchive-${VersionSemantic}.zip">
<Repository>$(GitRemoteRepository)</Repository>
</PushToGitRepositorySpecs>
-->
</ItemGroup>
<!--
**** DEPLOY STEPS ****
-->
<!--
The following ItemGroup defines which steps are taken during the deploy process. The order of the items in the item group
determines in which order the deploy steps are executed.
Each deploy step can define the following items:
- Properties - The semi-colon separated set of properties that should be passed to the script.
Properties are written as 'key=value'.
- Groups - All the groups that a given step belongs to. The user can elect to only run deploy steps for a given group.
- PreSteps - A semi-colon separated list of all additional scripts and their targets that should be executed before
the selected deploy step.
- PostSteps - A semi-colon separated list of all additional scripts and their targets that should be executed after
the selected deploy step.
The metadata to the script that is about to be executed is passed to each pre-step under the following properties:
- StepDescription : The full description of the step to be executed.
- StepId : The ID of the step. In general the name of the property that references the step file.
- StepName : The name of the step.
- StepPath : The full path to the script file for the step.
Additionally all the standard properties as seen below and the properties for the given deploy step are passed in.
Additional deploy steps can be defined by providing the path to the MsBuild script that should be executed
for that step, e.g. adding a deploy step that points to the 'c:\stuff\MyCoolScript.msbuild' will execute
that script.
Any properties defined by the 'Properties' section are pushed up.
-->
<ItemGroup Condition=" '$(ShouldLoadDeployStepsToExecute)' == 'true' ">
<!--
<DeployStepsToExecute Include="$(DeployStepsBuildTargetsAssembly)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.bootstrap;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsGenerateTargetsFile)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.bootstrap;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
-->
<DeployStepsToExecute Include="$(DeployStepsRestoreNuGet)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.restore;
prepare.restore.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<!--
The following steps need to be executed on the original branch (i.e. the branch we are interested in
building.
-->
<DeployStepsToExecute Include="$(DeployStepsPrepareVcsBranch)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.buildserver;
prepare.buildserver.vcssetbranch;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPrepareGetIssueIds)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.issueids;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<!--
All steps from here on may be executed on a different branch than the orginal branch we we started the
build on because we might have done some merging / restoring from a different repository.
-->
<DeployStepsToExecute Include="$(DeployStepsPrepareGetVersion)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.get;
prepare.get.version;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<!--
<DeployStepsToExecute Include="$(DeployStepsPrepareTagVcs)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
prepare;
prepare.vcs;
prepare.vcs.tag;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
-->
<DeployStepsToExecute Include="$(DeployStepsPrepareCopyNuGet)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.copy;
prepare.copy.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPrepareCopyFiles)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.copy;
prepare.copy.files;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPrepareCopyArchive)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.copy;
prepare.copy.archive;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPrepareFileHashes)">
<Properties>
</Properties>
<Groups>
prepare;
prepare.hash;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<!--
<DeployStepsToExecute Include="$(DeployStepsPushToTags)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.vcs.tags;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
-->
<DeployStepsToExecute Include="$(DeployStepsPushToNuget)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.package.nuget;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<!--
<DeployStepsToExecute Include="$(DeployStepsPushToDirectory)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.package.directory;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPushToSymbolServer)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.package.symbols;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPushToGitHubRelease)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.github;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
-->
<DeployStepsToExecute Include="$(DeployStepsPushToGitBranch)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.vcs.git.branch;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
<DeployStepsToExecute Include="$(DeployStepsPushToGitRepository)">
<Properties>
Configuration=$(ProductionConfiguration);
Platform=$(Platform);
</Properties>
<Groups>
deploy;
deploy.vcs.git.repository;
</Groups>
<PreSteps>
</PreSteps>
<PostSteps>
</PostSteps>
</DeployStepsToExecute>
</ItemGroup>
<!--
Define the scripts that should be executed when any one of the deploy steps fails.
Steps can be defined by providing the path to the MsBuild script that should be executed
for that step, e.g. adding a deploy step that points to the 'c:\stuff\MyCoolScript.msbuild' will execute
that script.
Any properties defined by the 'Properties' section are pushed up.
-->
<ItemGroup Condition=" '$(ShouldLoadDeployFailureStepsToExecute)' == 'true' ">
<!--
<DeployFailureStepsToExecute Include="">
<Properties>
</Properties>
</DeployFailureStepsToExecute>
-->
</ItemGroup>
<!--
The following item group stores metadata describing the custom deploy steps that are executed in the deploy process.
By providing this metadata it is possible for pre- and post-step actions to more clearly determine which step
they were attached to.
-->
<ItemGroup Condition=" '$(ShouldLoadAvailableStepMetadata)' == 'true' ">
<!--
<AvailableStepMetadata Include="$([System.IO.Path]::GetFileName('$(DirWorkspace)\my.deploy.step.msbuild'))">
<Description>
The description for my cool deploy step
</Description>
<Id></Id>
<Name>My deploy step</Name>
<Path>$(DirWorkspace)\my.deploy.step.msbuild</Path>
</AvailableStepMetadata>
-->
</ItemGroup>
<!--
*****************************************
* *
* TOOLS-OPS SPECIFIC SETTINGS *
* *
*****************************************
-->
<PropertyGroup>
<OpsConfigurationVersion>0.3</OpsConfigurationVersion>
</PropertyGroup>
</Project>