From 71f21d0fa0f61841c87a349baaca2a7aba0ba0a4 Mon Sep 17 00:00:00 2001 From: Frederick Muriuki Muriithi Date: Wed, 5 Nov 2025 12:17:00 -0600 Subject: gn-libs: (new issue) Jobs: Allow jobs cascades. --- issues/gn-libs/jobs-allow-job-cascades.gmi | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 issues/gn-libs/jobs-allow-job-cascades.gmi (limited to 'issues') diff --git a/issues/gn-libs/jobs-allow-job-cascades.gmi b/issues/gn-libs/jobs-allow-job-cascades.gmi new file mode 100644 index 0000000..f659f32 --- /dev/null +++ b/issues/gn-libs/jobs-allow-job-cascades.gmi @@ -0,0 +1,26 @@ +# Jobs: Allow Job Cascades + +## Tags + +* status: open +* priority: medium +* type: enhancement +* assigned: fredm, zsloan +* keywords: gn-libs, genenetwork, async jobs, asynchronous jobs, background jobs + +## Description + +Some jobs could require more than a single command/script to be run to complete. + +Rather than refactoring/rewriting the entire "async jobs" feature, I propose adding a way to note who started a job, i.e. +* the user, OR +* another job + +This could be tracked in an extra field in the database, say "started_by" which can have values of the form +* "user:" +* "job:" +where the parts in the angle bracket (i.e. "" and "") are replaced by actual ids. + +## Related Issues + +=> /issues/gn-libs/jobs-track-who-jobs-belong-to -- cgit 1.4.1