Tested Plane's auto-close and auto-archive across 9 weeks of virtual time #10286
Asmodeus14
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi! I'm building ChronoStack, an open-source tool that moves a whole Docker Compose stack forward in time together (Postgres
now(), Python's clock, Redis, …) while your schedulers keep running.Project automation is hard to test by hand: nobody waits a month to see whether a stale issue gets closed. So I ran the published
makeplane/plane-backend:stableimage (migrator, worker and beat-worker, unmodified, with Postgres, Valkey and RabbitMQ) and let Celery beat runarchive_and_close_old_issuesby itself every virtual day. No triggers or mocks.Setup: a project with auto-close after 1 month (to Cancelled) and auto-archive after 1 month, and one In Progress issue that nobody touches.
12/12 checks passed, and the 9 virtual weeks took about 3.5 minutes. Nothing was broken. One detail I confirmed along the way: auto-close refreshes
updated_at, so the archive timer starts from the close, not from the last human edit. That seems right to me, but it's worth knowing if anyone expects "archive 1 month after the last activity".The only change to Plane's setup was adding
--max-interval 1tocelery beat, so beat notices clock jumps within a second.The compose file, seed script, scenario and run report are here: https://github.com/Asmodeus14/ChronoStack/tree/main/docs/launch/outreach/plane (needs ChronoStack v0.1.0-alpha.3 or later, which handles one-shot containers like the migrator).
If it's useful, I'm happy to help turn it into a CI check for the automation tasks. And if anyone is on an Apple-silicon Mac,
chronostack doctoroutput would help me a lot: macOS is the one platform I haven't been able to test yet.All reactions