SoftEtherVPN/.ci/azure-pipelines/macos.yml

jobs:
- job: macOS
  pool:
    vmImage: macOS-latest
  steps:
  - script: brew install pkg-config cmake ninja ncurses readline libsodium openssl zlib
    displayName: 'Prepare environment'
  - script: '$(Build.SourcesDirectory)/.ci/azure-pipelines/macos_build.sh'
    env:
      SE_BUILD_NUMBER_TOKEN: $(BUILD_NUMBER_TOKEN)
    displayName: 'Build'
Azure Pipelines: add macOS build 2020-07-22 00:23:29 +03:00			`jobs:`
			`- job: macOS`
			`pool:`
			`vmImage: macOS-latest`
			`steps:`
CI: Switch from Ubuntu 16.04 to 18.04, install libsodium This commit: - Switches from Ubuntu 16.04 to 18.04 for all builds, mainly in order to use a more recent version of libsodium. - Installs libsodium, used by the WireGuard implementation. 2021-02-04 08:10:38 +03:00			`- script: brew install pkg-config cmake ninja ncurses readline libsodium openssl zlib`
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			`displayName: 'Prepare environment'`
			`- script: '$(Build.SourcesDirectory)/.ci/azure-pipelines/macos_build.sh'`
			`env:`
			`SE_BUILD_NUMBER_TOKEN: $(BUILD_NUMBER_TOKEN)`
Azure Pipelines: add macOS build 2020-07-22 00:23:29 +03:00			`displayName: 'Build'`