trigger: none
pr: none

variables:
  BASE_BRANCH: "master"
  CACHE_S3_PREFIX: "stack-nightly"
  CACHE_S3_VERSION: "v0.1.4"
  S3_BUCKET: "fpco-public-cache"
  AWS_REGION: "us-east-1"

jobs:
- template: ./.azure/azure-nightly-template-osx.yml
  parameters:
    name: macOS
    vmImage: macOS-10.14
    os: osx

- template: ./.azure/azure-nightly-template-linux.yml
  parameters:
    name: Linux
    vmImage: ubuntu-16.04
    os: linux

- template: ./.azure/azure-nightly-template-windows.yml
  parameters:
   name: Windows
   vmImage: vs2017-win2016
   os: windows

trigger: none
pr: none

schedules:
- cron: "0 0 * * *"
  displayName: Nightly build
  branches:
    include:
    - master
    - stable

variables:
  BASE_BRANCH: "master"
  CACHE_S3_PREFIX: "stack-nightly"
  CACHE_S3_VERSION: "v0.1.4"
  S3_BUCKET: "fpco-public-cache"
  AWS_REGION: "us-east-1"

jobs:
- template: ./.azure/azure-nightly-template-osx.yml
  parameters:
    name: macOS
    vmImage: macOS-10.14
    os: osx

- template: ./.azure/azure-nightly-template-linux.yml
  parameters:
    name: Linux
    vmImage: ubuntu-16.04
    os: linux

- template: ./.azure/azure-nightly-template-windows.yml
  parameters:
   name: Windows
   vmImage: vs2017-win2016
   os: windows

Enable nightly build for stable branch
Enable nightly build for stable branch

@borsboom pinged me that nightly pipeline seems to be missing in the
UI. Analyzing it further, I found that the nightly pipeline in the
dashboard has zero scheduled builds. The likely reason for this seems
to be because of new deployment of azure pipelines.

The good news is now we can control the nightly builds using the yaml
file itself (this wasn't possible before when we added azure builds to
stack initially). This PR does that and make sure we don't rely on UI
for the CI configuration anymore.
