bored-art-40741
05/29/2021, 2:58 AMjq
is on the executing machine. I'm really only using python
in this case to parse JSON cleanlyhundreds-father-404
05/29/2021, 3:08 AMbored-art-40741
05/29/2021, 3:21 AMProcess
, then capture certain files named in that JSON file into the output directory for that process. This is the Coursier resolve rule, where the possibility that the process was run remotely, and I depend on the files being fetched on the machine where the process was run, means I need to do a fair amount of work within the process itselfenough-analyst-54434
05/29/2021, 3:50 AMawait Get(PythonExecutable, InterpreterConstraints())
should do it. That will give you a path you can pass into your Process to do whatever with in a bash script.bored-art-40741
05/31/2021, 8:44 PMBashExecutable
strategy is buying me anything if the idea is that I'm supposed to be agnostic to remote execution where each Process
might run on a different executor. I might be missing something because I haven't dived deep, but I suspect that the JVM rules have just worked incidentally so far because there is no remote execution test, or because the remote machine is incidentally similar to the local machineenough-analyst-54434
05/31/2021, 9:05 PM#!/usr/bin/env bash
script today is just as good.digest = await Get(Digest, Address("my/custom/binary:target"))
and get a tool you wrote in-repo bootstrapped and useable by your rule.