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

jobs:
- job: Ubuntu_x64
  pool:
    vmImage: ubuntu-18.04
  steps:
  - script: sudo apt update && sudo apt-get -y install cmake gcc g++ ninja-build libncurses5-dev libreadline-dev libsodium-dev libssl-dev make zlib1g-dev
    displayName: 'Prepare environment'
  - script: "$(Build.SourcesDirectory)/.ci/azure-pipelines/linux_build.sh"
    env:
      SE_BUILD_NUMBER_TOKEN: $(BUILD_NUMBER_TOKEN)
    displayName: 'Build'
  - script: |
      .ci/appveyor-deb-install-test.sh
      sudo apt-get -y install autoconf libtool liblzo2-dev libpam-dev fping unzip # To build OpenVPN
      sudo BUILD_BINARIESDIRECTORY=$BUILD_BINARIESDIRECTORY .ci/start-se-openvpn.sh
      sudo BUILD_BINARIESDIRECTORY=$BUILD_BINARIESDIRECTORY .ci/run-openvpn-tests.sh
    displayName: 'Test'
Azure Pipelines: refactoring, adding windows target 2019-03-12 23:37:47 +03:00			`jobs:`
Azure Pipelines: Replace "x86_64" with "x64", for consistency with the codebase 2021-03-01 06:03:28 +03:00			`- job: Ubuntu_x64`
Azure Pipelines: refactoring, adding windows target 2019-03-12 23:37:47 +03:00			`pool:`
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			`vmImage: ubuntu-18.04`
Azure Pipelines: refactoring, adding windows target 2019-03-12 23:37:47 +03:00			`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: sudo apt update && sudo apt-get -y install cmake gcc g++ ninja-build libncurses5-dev libreadline-dev libsodium-dev libssl-dev make zlib1g-dev`
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/linux_build.sh"`
			`env:`
			`SE_BUILD_NUMBER_TOKEN: $(BUILD_NUMBER_TOKEN)`
Azure Pipelines: improve steps, use Ninja and designated build directory 2020-07-21 22:11:57 +03:00			`displayName: 'Build'`
			`- script: \|`
Azure Pipelines: refactoring, adding windows target 2019-03-12 23:37:47 +03:00			`.ci/appveyor-deb-install-test.sh`
Azure Pipelines: improve steps, use Ninja and designated build directory 2020-07-21 22:11:57 +03:00			`sudo apt-get -y install autoconf libtool liblzo2-dev libpam-dev fping unzip # To build OpenVPN`
			`sudo BUILD_BINARIESDIRECTORY=$BUILD_BINARIESDIRECTORY .ci/start-se-openvpn.sh`
			`sudo BUILD_BINARIESDIRECTORY=$BUILD_BINARIESDIRECTORY .ci/run-openvpn-tests.sh`
			`displayName: 'Test'`