chromium-dashboard/cron.yaml

cron:
- description: retrieve from chromium.googlesource.com chromium histograms
  url: /cron/histograms
  schedule: every day 04:00
- description: retrieve from UMA Cloud Storage data gathered yesterday
  url: /cron/metrics
  schedule: every day 22:00
- description: update list of Blink components
  url: /cron/update_blink_components
  schedule: every day 04:30
- description: sort metrics and load into memcache without request time limits
  url: /data/featurepopularity?refresh=1
  schedule: every 30 minutes synchronized
Initial commit of uma stuff 2013-04-12 21:19:21 +04:00			`cron:`
Added cron job to fetch chromium histograms 2015-02-10 20:31:50 +03:00			`- description: retrieve from chromium.googlesource.com chromium histograms`
			`url: /cron/histograms`
			`schedule: every day 04:00`
Initial commit of uma stuff 2013-04-12 21:19:21 +04:00			`- description: retrieve from UMA Cloud Storage data gathered yesterday`
			`url: /cron/metrics`
Run job at night 2016-03-12 01:27:49 +03:00			`schedule: every day 22:00`
Fix cron description 2017-06-27 00:57:19 +03:00			`- description: update list of Blink components`
Add cron job to update list of blink components 2017-06-21 07:03:49 +03:00			`url: /cron/update_blink_components`
Fix cron description 2017-06-27 00:57:19 +03:00			`schedule: every day 04:30`
Work around GAE deadline for feature popularity This request was never succeeding because it was taking longer than GAE's 60s deadline. There is no deadline when it is run as a cron, which allows it to succeed and put data into memcache for user requests to access. This change has already been deployed for about a week. 2019-10-28 23:09:38 +03:00			`- description: sort metrics and load into memcache without request time limits`
Work-around inability to check stackrank expected cache chunks. (#1063) * Work-around inability to check stackrank expected cache chunks. * Batch-get datapoints to improve memcache miss performance 2020-10-10 00:47:34 +03:00			`url: /data/featurepopularity?refresh=1`
Work around GAE deadline for feature popularity This request was never succeeding because it was taking longer than GAE's 60s deadline. There is no deadline when it is run as a cron, which allows it to succeed and put data into memcache for user requests to access. This change has already been deployed for about a week. 2019-10-28 23:09:38 +03:00			`schedule: every 30 minutes synchronized`