Closed frantjc closed 2 years ago
GitHub Actions (the "core" ones) are implemented using a special runs.plugin
field that means something special to the runner itself. This means any action that uses runs.plugin
will need to be implemented by sequence itself
will try to make a non-mess of this later
stream of consciousness:
struct
sWorkflow
,Job
,Step
to marshall yaml into.Planner
that takes saidstruct
s and turns them into someinterface
, say[]Runnable
[]Runnable
rather than yaml/config files, so keeping it genericuses
must clone the repo being used, potentially build it, and the run the actionuses
step, aget
step orput
step) need a way to communicate info back to sequence, soRunnable
s need a way to tell sequence if stdout should be parsed into some kind of response that sequence can then use. this is not new forget
orput
(concourse already does this for its resources), but is a new (and better imo) way of approaching running actions/dev/out
or something optionally mounted if the user wants the output from aRunnable
somewhere on their machineuses
ref so it can be reused