summary refs log tree commit diff
path: root/issues/gn-libs
diff options
context:
space:
mode:
Diffstat (limited to 'issues/gn-libs')
-rw-r--r--issues/gn-libs/jobs-allow-job-cascades.gmi26
-rw-r--r--issues/gn-libs/jobs-track-who-jobs-belong-to.gmi23
2 files changed, 49 insertions, 0 deletions
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:<user-id>"
+* "job:<job-id>"
+where the parts in the angle bracket (i.e. "<user-id>" and "<job-id>") are replaced by actual ids.
+
+## Related Issues
+
+=> /issues/gn-libs/jobs-track-who-jobs-belong-to
diff --git a/issues/gn-libs/jobs-track-who-jobs-belong-to.gmi b/issues/gn-libs/jobs-track-who-jobs-belong-to.gmi
new file mode 100644
index 0000000..00eaf21
--- /dev/null
+++ b/issues/gn-libs/jobs-track-who-jobs-belong-to.gmi
@@ -0,0 +1,23 @@
+# Jobs: Track Who Jobs Belong To
+
+## Tags
+
+* status: open
+* priority: medium
+* type: enhancement
+* assigned: fredm, zsloan
+* keywords: gn-libs, genenetwork, async jobs, asynchronous jobs, background jobs
+
+## Description
+
+Some features in Genenetwork require long-running processes to be triggered and run in the background. We have a way to trigger such background processes, but there is no way of tracking who started what job, and therefore, no real way for a user to list only their jobs.
+
+This issue will track the introduction of such tracking. This will enable the building new job-related functionality such as a user being able to:
+* list their past, unexpired jobs
+* delete past jobs
+* possibly rerun jobs that failed but are recoverable
+* see currently running jobs, and their status
+
+## Related Issues
+
+=> /issues/gn-libs/jobs-allow-job-cascades