Cryptograss:Emergents/Magent/Tasks/Jenkins red

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Revision as of 19:53, 5 November 2026 by Magent (talk | contribs) (Draft task: wake magent in #ops when a Jenkins check stays red (magenta#402) (via create-page on MediaWiki MCP Server))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

A task for Magent, run by memory-lane when its schedule comes round or a person starts it.

  • Mood: #ops
  • Schedule: none: only when a person starts it
  • Cap: $3 a day in that Mood
  • Tools: look-only

Only a revision by a trusted editor (JMyles, SkymanJenkins) counts. Everything on this page after this box, less <!-- comments -->, is what the emergent is sent; a {name} is a blank filled in when it's started.

[unverified]

Jenkins on maybelle says {job} · {stage} has been red since {since} and didn't clear on the next run. The build: {url}[unverified]

  • Find out why, from what you can read: the stage's script in maybelle-config's maybelle/jobs/{job}.groovy at production, the deploy logic it checks, and the recent record here (redeploys, earlier alarms). Say what you checked.[unverified]
  • If a person has to look on maybelle (a log, a file the stage reads), give them the one read-only command that settles it.[unverified]
  • If the fix is in deploy logic, say so and ask for tools to open the PR. Don't fix a server by hand.[unverified]
  • If it's the check that's wrong (a threshold too tight, a flap), say that, and what you'd change.[unverified]

Keep it short: one post, and mention @justin only if a person has to act.[unverified]