Switch the regular scheduler to support global scheduling, and have Peril handle the hooking

[orta]

Once I started to test out what scheduling looks like across many repos, I realized that what this does is set up an agenda queue per installations' scheduler settings. This won't scale, there needs to be a set number of queues that people can hook into instead.

Before

Where every org/scheduled task runs, which isn't going to scale, and I can't really delete old recurring jobs easily, instead offer only a few options:

For all days:

• "monday-morning"
• "monday-morning-est"
• "monday-evening"
• "tuesday-evening-est"
  ...

with GMT as default, maybe I could do: est, gmt, pdt and then try handle ust-1 from -12 to +12 onwards?

Then:

• "hourly"
• "daily"
• "weekly"
• "monthly"

Example JSON config:

{
  "$schema": "https://raw.githubusercontent.com/danger/peril/master/peril-settings-json.schema",

  "settings": {
    "modules": ["danger-plugin-spellcheck", "danger-plugin-yarn", "@slack/client", "semver-sort"]
  },
  "rules": {
    "create (ref_type == tag)": ["org/new_tag.ts", "org/updateDangerSystems.ts"],
    "pull_request.closed": "org/aeryn.ts",
    "pull_request": ["org/debug.ts", "org/changelog.ts"],
    "issue_comment": "org/markAsMergeOnGreen.ts",
    "issues.opened": "org/checkTemplate.ts",
    "status.success": "org/mergeOnGreen.ts"
  },
  "tasks": {
    "trigger-scheduler": "testing/trigger-scheduler.ts",
    "logger": "testing/logger.ts"
  },
  "scheduler": {
     "monday-morning": "logger",
     "daily": "trigger-scheduler"
  }
}

I might be able was able to make a query in mongo that can look for installations with the key match - so that can handle a lot of the work

[jlengstorf]

A few use cases for what we're planning to do with the scheduler in the Gatsby org:

• Checks for stale issues (daily)
• Auto-closing stale issues
• Checking for PRs and issues that haven't been responded to within X days

All of these would be daily checks, I think.

[orta]

Perfect yeah, makes sense 👍