Skip to content

Various Executors for Different Jobs #35

Open
@Southclaws

Description

@Southclaws

Now that #27 is on the way, the concept of an Executor exists.

So far, the only executor is CommandExecutor and it just executes task.Target jobs. It's a bit misleading because the task.Target is structured to be a "command" anyway but... that's another issue.

It could make sense to introduce more executors that don't just run a command but may perform other tasks that are easier to declaratively set up via Pico configuration instead of creating a whole new git repo for it.

I'm thinking of webhooks as a first, maybe integrations like Slack or Discord.

More feature-creep, I know. But it could be useful.

A Docker-specific executor may be useful, as more granular information can be acquired via the Docker Go library.

Food for thought anyway...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions