From b15a403c71963900e6232b22c5a51d48e7b1e751 Mon Sep 17 00:00:00 2001 From: George Kalpakas Date: Sat, 27 Apr 2019 12:56:34 +0300 Subject: [PATCH] ci(docs-infra): re-enable `aio_monitoring` CircleCI jobs and change time (#30168) The `aio_monitoring_next` CircleCI job was disabled due to a failure in [302254](https://circleci.com/gh/angular/angular/302254). It turned out the failure was caused because the job happened to run after a change had been merged into master and right before it was deployed to https://next.angular.io/ causing the tests not to match the deployed version. This commit re-enables the job and moves it to a different time, when it is less likely that PRs will be being merged (and thus reducing the risk of a similar timming issue). Fixes #30101 PR Close #30168 --- .circleci/config.yml | 36 +++++++++++++++++------------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 752ecb1947..0e69182d91 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -712,25 +712,23 @@ workflows: cron: "0 * * * *" filters: *publish_branches_filter -# This job is currently disabled due to a version skew problem. -# More info is available here: https://github.com/angular/angular/issues/30101 -# aio_monitoring: -# jobs: -# - setup -# - aio_monitoring_stable: -# requires: -# - setup -# - aio_monitoring_next: -# requires: -# - setup -# triggers: -# - schedule: -# # Runs AIO monitoring jobs at 00:00AM every day. -# cron: "0 0 * * *" -# filters: -# branches: -# only: -# - master + aio_monitoring: + jobs: + - setup + - aio_monitoring_stable: + requires: + - setup + - aio_monitoring_next: + requires: + - setup + triggers: + - schedule: + # Runs AIO monitoring jobs at 10:00AM every day. + cron: "0 10 * * *" + filters: + branches: + only: + - master # TODO: # - don't build the g3 branch