Azure Pipelines scheduled triggers need to be migrated to YAML #17342
Comments
Hopefully this isn't true :) |
|
https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?tabs=yaml&view=azure-devops#scheduled-triggers has been updated now, I'll try to put a PR together. |
Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes #17342.
|
I've sent #18442, and when I went to remove the triggers in the screenshot at the top of this issue, I found they weren't there, not even in a disabled state. @thejohnjansen @mustjab did either of you remove them while trying to debug #18397? It doesn't matter since they'll be replaced, but it is odd because in my safari-technology-preview-updater repo I had to remove them manually. |
Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes #17342.
|
#18442 didn't work, a build should have been triggered 06:15 UTC (15 minutes ago) but wasn't. |
|
Since the trigger originally configured in the Azure DevOps UI are no longer there, fixing this has become urgent :( |
|
There's some chance the reason it didn't work was because the epochs/six_hourly branch wasn't updated in time. The configuration was on master, but locally I didn't see the epochs/six_hourly ref update a bit after 06:00, and looking at webhook activity it looks like it might have been updated at 06:32. Waiting for another 6 hours to see if the next one will be triggered. |
|
(The possible reason being that if the configuration isn't on the branch being triggered, it doesn't work.) |
|
To verify that the configuration is working at all currently I've triggered a manual build for Edge Dev, Edge Canary, Safari and Safari Technology Preview: https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=27211 |
As it is, it's only possible to run both of them: #17342 (comment)
|
Alright, it worked, https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=27268 is in progress! |
…18445) As it is, it's only possible to run both of them: #17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming.
…ds to YAML, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Migrate scheduled builds to YAML (#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests/wpt#17342. -- wpt-commits: b16bc5597bb9981c3bd29ca3209979df0c9c24fe wpt-pr: 18442
…riggers for Edge Dev/Canary, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445) As it is, it's only possible to run both of them: web-platform-tests/wpt#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming. -- wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4 wpt-pr: 18445
…ds to YAML, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Migrate scheduled builds to YAML (#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests/wpt#17342. -- wpt-commits: b16bc5597bb9981c3bd29ca3209979df0c9c24fe wpt-pr: 18442
…riggers for Edge Dev/Canary, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445) As it is, it's only possible to run both of them: web-platform-tests/wpt#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming. -- wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4 wpt-pr: 18445
…s#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests#17342.
…eb-platform-tests#18445) As it is, it's only possible to run both of them: web-platform-tests#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming.
…ds to YAML, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Migrate scheduled builds to YAML (#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests/wpt#17342. -- wpt-commits: b16bc5597bb9981c3bd29ca3209979df0c9c24fe wpt-pr: 18442 UltraBlame original commit: d3ff9a191f89e8fcdc40fbd7b574be12eb06228a
…riggers for Edge Dev/Canary, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445) As it is, it's only possible to run both of them: web-platform-tests/wpt#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming. -- wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4 wpt-pr: 18445 UltraBlame original commit: 097066d228b2fbe5da8346271578e3ed36566697
…ds to YAML, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Migrate scheduled builds to YAML (#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests/wpt#17342. -- wpt-commits: b16bc5597bb9981c3bd29ca3209979df0c9c24fe wpt-pr: 18442 UltraBlame original commit: d3ff9a191f89e8fcdc40fbd7b574be12eb06228a
…riggers for Edge Dev/Canary, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445) As it is, it's only possible to run both of them: web-platform-tests/wpt#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming. -- wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4 wpt-pr: 18445 UltraBlame original commit: 097066d228b2fbe5da8346271578e3ed36566697
…ds to YAML, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Migrate scheduled builds to YAML (#18442) Based on another migration which worked: foolip/safari-technology-preview-updater@259eff3 Fixes web-platform-tests/wpt#17342. -- wpt-commits: b16bc5597bb9981c3bd29ca3209979df0c9c24fe wpt-pr: 18442 UltraBlame original commit: d3ff9a191f89e8fcdc40fbd7b574be12eb06228a
…riggers for Edge Dev/Canary, a=testonly Automatic update from web-platform-tests [Azure Pipelines] Differentiate manual triggers for Edge Dev/Canary (#18445) As it is, it's only possible to run both of them: web-platform-tests/wpt#17342 (comment) This also renames the Edge Dev job and artifacts so that Edge stable can later be added without further renaming. -- wpt-commits: c1e89362cb351be0ea9239e38cf5830e104ba1f4 wpt-pr: 18445 UltraBlame original commit: 097066d228b2fbe5da8346271578e3ed36566697
Looking at triggers in the pipeline editor today I see this:
However, the link leads to https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema and I can't see any documentation on how to migrate the schedule triggers to YAML.
@mustjab @thejohnjansen could you ask if this already works but isn't documented, or what we should do?
It appears that the scheduled runs are still getting triggered, but this could turn urgent if at any point they stop working, since the workaround before has been to make an edit and save them again.
The text was updated successfully, but these errors were encountered: