AMajor/SoftEtherVPN
1
0
Fork 0
mirror of https://github.com/SoftEtherVPN/SoftEtherVPN.git synced 2024-11-14 13:40:39 +03:00
Code Releases Activity
0325c13c40
SoftEtherVPN/.ci/azure-pipelines/windows-steps.yml

46 lines
1.3 KiB
YAML
Raw Normal View History

Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
parameters:
Azure Pipelines: install OpenSSL and zlib through vcpkg on Windows This commit also changes the x86 build so that it uses the "amd64_x86" toolchain, for potentially better build performance. The architecture is now appended to the installers.
2020-07-28 00:34:34 +03:00
- name: architecture
type: string
Azure Pipelines: use "clang-cl" for Windows builds Now that we can successfully compile with Clang, there's probably no reason to stick with MSVC.
2020-08-16 03:15:25 +03:00
- name: compilerPath
type: string
Azure Pipelines: install OpenSSL and zlib through vcpkg on Windows This commit also changes the x86 build so that it uses the "amd64_x86" toolchain, for potentially better build performance. The architecture is now appended to the installers.
2020-07-28 00:34:34 +03:00
- name: vcpkgTriplet
type: string
- name: vcvarsPath
Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
type: string
steps:
Azure Pipelines: install OpenSSL and zlib through vcpkg on Windows This commit also changes the x86 build so that it uses the "amd64_x86" toolchain, for potentially better build performance. The architecture is now appended to the installers.
2020-07-28 00:34:34 +03:00
- task: Cache@2
inputs:
key: '"vcpkg-installed-windows-${{parameters.architecture}}"'
path: 'C:/vcpkg/installed'
displayName: 'Environment storage'
- script: |
vcpkg install openssl zlib --triplet ${{parameters.vcpkgTriplet}}
workingDirectory: C:/vcpkg
displayName: 'Prepare environment'
Azure Pipelines: Retrieve build number from server, pass it to CMake The script on our server bumps the build number for every new version + commit combination. Each combination is associated to a unique build number and vice versa. There's a separate counter for each version. The reason why we cannot just use "git describe --tags --dirty" is because it relies on the last tag's name and generates a string like "5.01.9674-212-g54280853". What we want, instead, is the last part of the version to be increased for every build. Then, once we consider the branch stable enough, we create a tag like "5.01" and bump the version immediately after the new release. Please note that for pull requests the build number will always be 0, because the secret token is only available in the Nightly pipeline.
2021-02-19 23:22:48 +03:00
- script: '$(Build.SourcesDirectory)/.ci/azure-pipelines/windows_build.bat'
env:
ARCHITECTURE: ${{parameters.architecture}}
COMPILER_PATH: ${{parameters.compilerPath}}
VCPKG_TRIPLET: ${{parameters.vcpkgTriplet}}
VCVARS_PATH: ${{parameters.vcvarsPath}}
SE_BUILD_NUMBER_TOKEN: $(BUILD_NUMBER_TOKEN)
Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
displayName: 'Build'
- powershell: |
Azure Pipelines: install OpenSSL and zlib through vcpkg on Windows This commit also changes the x86 build so that it uses the "amd64_x86" toolchain, for potentially better build performance. The architecture is now appended to the installers.
2020-07-28 00:34:34 +03:00
. .ci/appveyor-vpntest.ps1
Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
displayName: 'Test'
- task: CopyFiles@2
inputs:
sourceFolder: '$(Build.BinariesDirectory)'
contents: '?(*.exe|*.se2|*.pdb)'
Azure Pipelines: build Windows installers and provide them as artifacts
2020-07-27 09:10:20 +03:00
TargetFolder: '$(Build.StagingDirectory)/binaries'
Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
flattenFolders: true
- task: PublishBuildArtifacts@1
inputs:
Azure Pipelines: build Windows installers and provide them as artifacts
2020-07-27 09:10:20 +03:00
pathtoPublish: '$(Build.StagingDirectory)/binaries'
Azure Pipelines: templatize Windows steps
2020-07-21 23:01:19 +03:00
artifactName: 'Binaries'
Azure Pipelines: build Windows installers and provide them as artifacts
2020-07-27 09:10:20 +03:00
- task: PublishBuildArtifacts@1
inputs:
pathtoPublish: '$(Build.StagingDirectory)/installers'
artifactName: 'Installers'
Copy Permalink