OpenTTD-patches/azure-pipelines/templates/release-manifest.yml

parameters:
  IsStableRelease: false

steps:
- task: DownloadBuildArtifacts@0
  displayName: 'Download all bundles'
  inputs:
    downloadType: specific
    itemPattern: 'bundles/*'
    downloadPath: '$(Build.ArtifactStagingDirectory)'
- ${{ if eq(parameters.IsStableRelease, true) }}:
  - script: |
      touch .is_stable
    displayName: 'Mark as stable release'
- script: |
    set -ex
    ./azure-pipelines/manifest.sh ../a/bundles/
    mkdir -p build/bundles
    mv manifest.yaml build/bundles/
  displayName: 'Create manifest.yaml'
Fix: [AzurePipelines] manifest.sh didn't know when it was a stable release In result, the name of the release was wrong, causing confusing in tools using the manifest.yaml. 2019-02-09 19:13:28 +00:00			`parameters:`
			`IsStableRelease: false`

Add: [AzurePipeline] introducing a release pipeline This release pipeline creates all the official release binaries, and publishes them as artifacts. Currently it can only produce nightlies and custom builds; stable/testing release binaries are untested. This commit also splits up the pipeline in small bits, to both improve readability, and to share code with the CI pipeline where possible. 2019-01-05 19:11:29 +00:00			`steps:`
			`- task: DownloadBuildArtifacts@0`
			`displayName: 'Download all bundles'`
			`inputs:`
			`downloadType: specific`
			`itemPattern: 'bundles/*'`
			`downloadPath: '$(Build.ArtifactStagingDirectory)'`
Fix: [AzurePipelines] manifest.sh didn't know when it was a stable release In result, the name of the release was wrong, causing confusing in tools using the manifest.yaml. 2019-02-09 19:13:28 +00:00			`- ${{ if eq(parameters.IsStableRelease, true) }}:`
			`- script: \|`
			`touch .is_stable`
			`displayName: 'Mark as stable release'`
Add: [AzurePipeline] introducing a release pipeline This release pipeline creates all the official release binaries, and publishes them as artifacts. Currently it can only produce nightlies and custom builds; stable/testing release binaries are untested. This commit also splits up the pipeline in small bits, to both improve readability, and to share code with the CI pipeline where possible. 2019-01-05 19:11:29 +00:00			`- script: \|`
			`set -ex`
			`./azure-pipelines/manifest.sh ../a/bundles/`
Fix: [AzurePipelines] switch the CI / CD to CMake too This also means dropping Debian/jessie, as it has a CMake that is too old (3.0), with no real path to upgrade. 2019-04-07 10:01:32 +00:00			`mkdir -p build/bundles`
			`mv manifest.yaml build/bundles/`
Add: [AzurePipeline] introducing a release pipeline This release pipeline creates all the official release binaries, and publishes them as artifacts. Currently it can only produce nightlies and custom builds; stable/testing release binaries are untested. This commit also splits up the pipeline in small bits, to both improve readability, and to share code with the CI pipeline where possible. 2019-01-05 19:11:29 +00:00			`displayName: 'Create manifest.yaml'`