pulsar/script/vsts/release-branch-build.yml

trigger:
  - master
  - 1.* # VSTS only supports wildcards at the end
  - electron-*
pr: none # no PR triggers

jobs:
  - job: GetReleaseVersion
    pool:
      vmImage: 'ubuntu-latest'
    steps:
      # This has to be done separately because VSTS inexplicably
      # exits the script block after `npm ci` completes.
      - script: |
          cd script/vsts
          npm ci
        displayName: npm ci
      - script: node script/vsts/get-release-version.js
        name: Version

  # Import OS-specific build definitions.
  - template: platforms/windows.yml
  - template: platforms/macos.yml
  - template: platforms/linux.yml

  - job: UploadArtifacts
    pool:
      vmImage: 'ubuntu-latest'

    dependsOn:
      - GetReleaseVersion
      - Windows_RendererTests
      - Linux
      - macOS_tests

    variables:
      ReleaseVersion: $[ dependencies.GetReleaseVersion.outputs['Version.ReleaseVersion'] ]
      IsReleaseBranch: $[ dependencies.GetReleaseVersion.outputs['Version.IsReleaseBranch'] ]
      IsSignedZipBranch: $[ dependencies.GetReleaseVersion.outputs['Version.IsSignedZipBranch'] ]

    steps:
      # This has to be done separately because VSTS inexplicably
      # exits the script block after `npm ci` completes.
      - script: |
          cd script/vsts
          npm ci
        env:
          GITHUB_TOKEN: $(GITHUB_TOKEN)
        displayName: npm ci

      - task: DownloadBuildArtifacts@0
        inputs:
          itemPattern: '**'
          downloadType: 'specific'
        displayName: Download Release Artifacts

      - script: |
          node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom-staging"
        env:
          GITHUB_TOKEN: $(GITHUB_TOKEN)
          ATOM_RELEASE_VERSION: $(ReleaseVersion)
          ATOM_RELEASES_S3_KEY: $(ATOM_RELEASES_S3_KEY)
          ATOM_RELEASES_S3_SECRET: $(ATOM_RELEASES_S3_SECRET)
          ATOM_RELEASES_S3_BUCKET: $(ATOM_RELEASES_S3_BUCKET)
          PACKAGE_CLOUD_API_KEY: $(PACKAGE_CLOUD_API_KEY)
        displayName: Create Draft Release
        condition: and(succeeded(), eq(variables['Atom.AutoDraftRelease'], 'true'), eq(variables['IsReleaseBranch'], 'true'))

      - script: |
          node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --assets-path "$(System.ArtifactsDirectory)" --s3-path "vsts-artifacts/$(Build.BuildId)/"
        env:
          ATOM_RELEASE_VERSION: $(ReleaseVersion)
          ATOM_RELEASES_S3_KEY: $(ATOM_RELEASES_S3_KEY)
          ATOM_RELEASES_S3_SECRET: $(ATOM_RELEASES_S3_SECRET)
          ATOM_RELEASES_S3_BUCKET: $(ATOM_RELEASES_S3_BUCKET)
        displayName: Upload CI Artifacts to S3
        condition: and(succeeded(), eq(variables['IsSignedZipBranch'], 'true'))
Create stable and beta release build definition for VSTS 2018-07-26 17:00:53 +03:00			`trigger:`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- master`
			`- 1.* # VSTS only supports wildcards at the end`
			`- electron-*`
no PR triggers on release builds 2020-07-10 07:14:12 +03:00			`pr: none # no PR triggers`
Create stable and beta release build definition for VSTS 2018-07-26 17:00:53 +03:00
Fix strategy and timeout Changing the matrix to match new strategy schema. and moving timoutInMinutes up. 2018-08-31 22:13:57 +03:00			`jobs:`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- job: GetReleaseVersion`
Using windows-latest for vmImage 2020-07-03 08:04:46 +03:00			`pool:`
CI: Use 'ubuntu-latest' for GetReleaseVersion Ubuntu is much faster than Windows at installing many small files, such as during `git clone` and `npm install`. 2020-07-26 01:32:18 +03:00			`vmImage: 'ubuntu-latest'`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`steps:`
			`# This has to be done separately because VSTS inexplicably`
CI: Use `npm ci` rather than `npm install` `npm ci` doesn't try to reconcile package.json with package-lock.json, nor with any existing packages in `node_modules`. `npm ci` simply deletes `node_modules` and uses the packages from `package-lock.json`. As a result, `npm ci` is much, much faster than `npm install`. We should use it wherever possible. 2020-07-26 20:13:06 +03:00			# exits the script block after `npm ci` completes.
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- script: \|`
CI: Use forward-slashes in paths (cross-platform) Backslashes ("\") can be interpreted as escape characters on Unix (Linux, macOS). Replace with forward-slashes, "/", which are interpreted the same (as directory separators) on all OSes, at least in arguments to commands such as `cd` and `node`. 2020-07-26 01:24:40 +03:00			`cd script/vsts`
CI: Use `npm ci` rather than `npm install` `npm ci` doesn't try to reconcile package.json with package-lock.json, nor with any existing packages in `node_modules`. `npm ci` simply deletes `node_modules` and uses the packages from `package-lock.json`. As a result, `npm ci` is much, much faster than `npm install`. We should use it wherever possible. 2020-07-26 20:13:06 +03:00			`npm ci`
			`displayName: npm ci`
CI: Use forward-slashes in paths (cross-platform) Backslashes ("\") can be interpreted as escape characters on Unix (Linux, macOS). Replace with forward-slashes, "/", which are interpreted the same (as directory separators) on all OSes, at least in arguments to commands such as `cd` and `node`. 2020-07-26 01:24:40 +03:00			`- script: node script/vsts/get-release-version.js`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`name: Version`
Create stable and beta release build definition for VSTS 2018-07-26 17:00:53 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`# Import OS-specific build definitions.`
			`- template: platforms/windows.yml`
			`- template: platforms/macos.yml`
			`- template: platforms/linux.yml`
Add GetReleaseVersion step to set ReleaseVersion variable 2018-07-26 17:31:34 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- job: UploadArtifacts`
			`pool:`
CI: Use 'ubuntu-latest' to upload artifacts This should be marginally faster. No need to run on Windows. 2020-07-26 01:35:34 +03:00			`vmImage: 'ubuntu-latest'`
Enable S3 artifact uploads for builds on master 2018-08-02 03:35:58 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`dependsOn:`
			`- GetReleaseVersion`
CI: Fix Windows job names Also make sure "Release" job depends on successful Windows tests, not just on the Windows build job, before/regardless of testing. 2020-08-04 19:12:09 +03:00			`- Windows_RendererTests`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- Linux`
			`- macOS_tests`
Rolling back to vs2015 image For some reason the vs2017 image can't build with python 2.7 and gyp properly. 2018-08-31 22:50:00 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`variables:`
			`ReleaseVersion: $[ dependencies.GetReleaseVersion.outputs['Version.ReleaseVersion'] ]`
			`IsReleaseBranch: $[ dependencies.GetReleaseVersion.outputs['Version.IsReleaseBranch'] ]`
			`IsSignedZipBranch: $[ dependencies.GetReleaseVersion.outputs['Version.IsSignedZipBranch'] ]`
Enable S3 artifact uploads for builds on master 2018-08-02 03:35:58 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`steps:`
			`# This has to be done separately because VSTS inexplicably`
CI: Use `npm ci` rather than `npm install` `npm ci` doesn't try to reconcile package.json with package-lock.json, nor with any existing packages in `node_modules`. `npm ci` simply deletes `node_modules` and uses the packages from `package-lock.json`. As a result, `npm ci` is much, much faster than `npm install`. We should use it wherever possible. 2020-07-26 20:13:06 +03:00			# exits the script block after `npm ci` completes.
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- script: \|`
CI: Use forward-slashes in paths (cross-platform) Backslashes ("\") can be interpreted as escape characters on Unix (Linux, macOS). Replace with forward-slashes, "/", which are interpreted the same (as directory separators) on all OSes, at least in arguments to commands such as `cd` and `node`. 2020-07-26 01:24:40 +03:00			`cd script/vsts`
CI: Use `npm ci` rather than `npm install` `npm ci` doesn't try to reconcile package.json with package-lock.json, nor with any existing packages in `node_modules`. `npm ci` simply deletes `node_modules` and uses the packages from `package-lock.json`. As a result, `npm ci` is much, much faster than `npm install`. We should use it wherever possible. 2020-07-26 20:13:06 +03:00			`npm ci`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`env:`
			`GITHUB_TOKEN: $(GITHUB_TOKEN)`
CI: Use `npm ci` rather than `npm install` `npm ci` doesn't try to reconcile package.json with package-lock.json, nor with any existing packages in `node_modules`. `npm ci` simply deletes `node_modules` and uses the packages from `package-lock.json`. As a result, `npm ci` is much, much faster than `npm install`. We should use it wherever possible. 2020-07-26 20:13:06 +03:00			`displayName: npm ci`
Enable S3 artifact uploads for builds on master 2018-08-02 03:35:58 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- task: DownloadBuildArtifacts@0`
			`inputs:`
			`itemPattern: '**'`
			`downloadType: 'specific'`
			`displayName: Download Release Artifacts`
Enable S3 artifact uploads for builds on master 2018-08-02 03:35:58 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- script: \|`
CI: Use forward-slashes in paths (cross-platform) Backslashes ("\") can be interpreted as escape characters on Unix (Linux, macOS). Replace with forward-slashes, "/", which are interpreted the same (as directory separators) on all OSes, at least in arguments to commands such as `cd` and `node`. 2020-07-26 01:24:40 +03:00			`node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom-staging"`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`env:`
			`GITHUB_TOKEN: $(GITHUB_TOKEN)`
			`ATOM_RELEASE_VERSION: $(ReleaseVersion)`
			`ATOM_RELEASES_S3_KEY: $(ATOM_RELEASES_S3_KEY)`
			`ATOM_RELEASES_S3_SECRET: $(ATOM_RELEASES_S3_SECRET)`
			`ATOM_RELEASES_S3_BUCKET: $(ATOM_RELEASES_S3_BUCKET)`
			`PACKAGE_CLOUD_API_KEY: $(PACKAGE_CLOUD_API_KEY)`
			`displayName: Create Draft Release`
			`condition: and(succeeded(), eq(variables['Atom.AutoDraftRelease'], 'true'), eq(variables['IsReleaseBranch'], 'true'))`
Enable S3 artifact uploads for builds on master 2018-08-02 03:35:58 +03:00
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`- script: \|`
CI: Use forward-slashes in paths (cross-platform) Backslashes ("\") can be interpreted as escape characters on Unix (Linux, macOS). Replace with forward-slashes, "/", which are interpreted the same (as directory separators) on all OSes, at least in arguments to commands such as `cd` and `node`. 2020-07-26 01:24:40 +03:00			`node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --assets-path "$(System.ArtifactsDirectory)" --s3-path "vsts-artifacts/$(Build.BuildId)/"`
Auto-format yaml files 2019-06-12 12:27:03 +03:00			`env:`
			`ATOM_RELEASE_VERSION: $(ReleaseVersion)`
			`ATOM_RELEASES_S3_KEY: $(ATOM_RELEASES_S3_KEY)`
			`ATOM_RELEASES_S3_SECRET: $(ATOM_RELEASES_S3_SECRET)`
			`ATOM_RELEASES_S3_BUCKET: $(ATOM_RELEASES_S3_BUCKET)`
			`displayName: Upload CI Artifacts to S3`
			`condition: and(succeeded(), eq(variables['IsSignedZipBranch'], 'true'))`