Property:Deploy note
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
Text What a pull request needs deployed, from the Deploy line at the foot of its description. Set by Template:PR.[unverified]
P
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane), after #451; no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations +
redeploy maybelle (memory-lane); no migrations. Then save the four Conflict task pages as a trusted editor, or nothing wakes +
** merge, then deploy hunter. That's about 4 minutes now that the build cache works again. re's poller restarts with the new default.
+
maybelle, then hunter. After hunter, magent checks: +
maybelle; delivery-kid for its uptime. +
** hunter (the whole playbook, not just the agency container), plus maybelle for blu's key line. Afterwards:
+
** hunter, with an image rebuild, since the Dockerfile changed: about 11 minutes cold. Afterwards:
+
** hunter only, and it can go in the same hunter redeploy as #222. maybelle needs nothing now: its next deploy reads `people` and writes the same `allowed_signers` and wiki names. The other servers' SSH announcements re-render identically.
+
** hunter only.
+
hunter, with the image rebuild. +