Changeset - r23296:c8962a390a02
[Not reviewed]
master
0 3 0
Patric Stout - 6 years ago 2019-02-09 19:13:28
truebrain@openttd.org
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.
3 files changed with 11 insertions and 1 deletions:
0 comments (0 inline, 0 general)
azure-pipelines/manifest.sh
Show inline comments
 
@@ -15,7 +15,7 @@ if [ ! -e .version ] || [ ! -e .release_
 
fi
 

	
 
# Find the name based on the version
 
if [ "${ISSTABLERELEASE}" = "true" ]; then
 
if [ -e .is_stable ]; then
 
    isTesting=$(cat .version | grep "RC\|beta" || true)
 
    if [ -z "${isTesting}" ]; then
 
        NAME="stable"
azure-pipelines/templates/release-manifest.yml
Show inline comments
 
parameters:
 
  IsStableRelease: false
 

	
 
steps:
 
- task: DownloadBuildArtifacts@0
 
  displayName: 'Download all bundles'
 
@@ -5,6 +8,10 @@ steps:
 
    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/
azure-pipelines/templates/release.yml
Show inline comments
 
@@ -164,6 +164,9 @@ jobs:
 
  steps:
 
  - template: release-fetch-source.yml
 
  - template: release-manifest.yml
 
    ${{ if eq(parameters.IsStableRelease, true) }}:
 
      parameters:
 
        IsStableRelease: true
 
  - template: release-bundles.yml
 
    parameters:
 
      CalculateChecksums: false
0 comments (0 inline, 0 general)