make the toolforge-jobs module just a wrapper around the python script

Author: siddharthvp

jobs.ts

@@ -22,7 +22,6 @@
     "async-redis": "^1.1.7",
     "eventsource": "^1.0.7",
     "express": "^4.17.1",
-    "js-yaml": "^4.1.0",
     "jsdom": "^16.2.1",
     "minimist": "^1.2.5",
     "moment": "^2.29.1",

package-lock.json

@@ -0,0 +1,25 @@
+import {exec} from "child_process";
+import {mapPath} from "./utils";
+import {log} from "./botbase";
+
+const pythonInterpreterPath = '~/www/python/venv/bin/python';
+const toolforgeJobsScriptPath = '~/toolforge-jobs.py';
+const toolforgeJobsCfgPath = '~/toolforge-jobs-framework-cli.cfg';
+
+/**
+ * This relies on the fact that python is available in node16 container.
+ * The python venv is already setup. We run the toolforge-jobs.py script
+ * which is a copy of /usr/bin/toolforge-jobs copied to tool's home directory as /usr/bin is
+ * not mounted on the container.
+ */
+export function toolforgeJobs(...args: string[]) {
+    exec(mapPath(`${pythonInterpreterPath} ${toolforgeJobsScriptPath} --cfg ${toolforgeJobsCfgPath} ${args.join(' ')}`), function (err, stdout, stderr) {
+        if (stdout) {
+            console.log(stdout);
+        }
+        if (stderr) {
+            log(`[E] Error in toolforge-jobs`);
+            console.log(stderr);
+        }
+    });
+}