SoftEtherVPN/.ci/azure-pipelines/macos_build.sh

#!/bin/bash

if [[ "${#SE_BUILD_NUMBER_TOKEN}" -eq 64 ]]; then
	VERSION=$(python "version.py")
	BUILD_NUMBER=$(curl "https://softether.network/get-build-number?commit=${BUILD_SOURCEVERSION}&version=${VERSION}&token=${SE_BUILD_NUMBER_TOKEN}")
else
	BUILD_NUMBER=0
fi

cd ${BUILD_BINARIESDIRECTORY}

cmake -G "Ninja" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_NUMBER=${BUILD_NUMBER} -DOPENSSL_ROOT_DIR="/usr/local/opt/openssl" ${BUILD_SOURCESDIRECTORY}
cmake --build .
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			`#!/bin/bash`

			`if [[ "${#SE_BUILD_NUMBER_TOKEN}" -eq 64 ]]; then`
			`VERSION=$(python "version.py")`
			`BUILD_NUMBER=$(curl "https://softether.network/get-build-number?commit=${BUILD_SOURCEVERSION}&version=${VERSION}&token=${SE_BUILD_NUMBER_TOKEN}")`
			`else`
			`BUILD_NUMBER=0`
			`fi`

			`cd ${BUILD_BINARIESDIRECTORY}`

			`cmake -G "Ninja" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_NUMBER=${BUILD_NUMBER} -DOPENSSL_ROOT_DIR="/usr/local/opt/openssl" ${BUILD_SOURCESDIRECTORY}`
			`cmake --build .`