explain cron workaround (#2565)

This commit is contained in:
Gary Verhaegen 2019-08-16 13:05:11 +01:00 committed by GitHub
parent 992b46c8f2
commit 78d6ac04b5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -2,22 +2,27 @@
# Do not run on PRs # Do not run on PRs
pr: none pr: none
# Do not run on merge to master # Do not run on merge to master
trigger: none trigger: none
# Do run on a schedule (hourly) # Do run on a schedule (hourly)
# This feature seems completely broken, so for the time being the schedule has
# been defined manually in the Azure Pipelines Web UI. Note that Azure
# Pipelines sometimes spontaneously decides to silently delete that
# configuration, so someone should keep an eye on that.
# #
# The setup is kept here in case it suddenly starts to work. # This is currently (2019-08-15) broken on Azure for GitHub-hosted repos. It
schedules: # does, however, work as expected for Azure-hosted repos. As a workaround, we
- cron: "0 * * * *" # have created a repo inside Azure that contains an `azure-pipelines.yml` file
displayName: hourly cron # that just triggers this job.
branches: #
include: # When the situation is resolved, delete that repo in Azure and uncomment the
- master # following. In the meantime, this should stay commented so we avoid running
always: true # jobs twice when Azure fixes this issue.
#schedules:
#- cron: "0 * * * *"
# displayName: hourly cron
# branches:
# include:
# - master
# always: true
jobs: jobs:
- job: docs - job: docs