Act
This tool is a command-line runner that executes automation workflows locally within isolated container environments. By parsing workflow definition files and translating them into executable shell scripts, it allows developers to validate pipeline logic and configuration changes directly on their machines before committing code to a remote repository.
The runner distinguishes itself by providing a simulation engine that mimics remote CI triggers and event payloads, enabling the testing of complex conditional logic without requiring cloud infrastructure. It supports granular control over the execution environment, allowing users to specify custom container images, inject secrets, and map local directory structures to ensure consistent module resolution. Furthermore, it facilitates integration with private enterprise infrastructure by supporting secure authentication and custom container engine configurations.
The project provides operational controls for troubleshooting, such as the ability to isolate and execute individual workflow tasks by name. It manages the lifecycle of ephemeral runner instances through standard socket interfaces, ensuring that local development environments remain synchronized with the requirements of production pipelines.
Features
- Containerized Workflow Runners - Runs automation tasks inside isolated container environments that mirror the configuration of remote CI systems.
- Containerized Task Executors - A runtime environment that maps workflow definitions to isolated container instances to ensure consistent execution across different development machines.
- Docker Socket Orchestrators - Communicates with container runtimes via standard socket interfaces to manage the lifecycle of ephemeral runner instances.
- Local Workflow Runners - The automation runner enables the execution of workflow files directly on a local machine to verify automation logic and configuration changes before committing code.
- Environment Simulation Tools - Configuring specific container images and runtime settings to ensure automation tasks execute within the exact environment requirements of your production pipeline.
- Runner Image Specifications - The automation runner allows users to specify custom container images for workflow runners to ensure automation tasks execute within the exact environment requirements needed for builds.
- Event-Driven Testing Frameworks - Simulating complex workflow triggers by passing custom data payloads to verify how automation logic responds to various real-world event types.
- Cross-Platform Automation Tools - A portable execution layer that bridges local development environments with container runtimes to standardize build and test processes across diverse systems.
- Local Workflow Runners - A command-line tool that executes automation workflows locally within containerized environments to verify logic before pushing code to remote repositories.
- CI/CD Simulation Engines - A development utility that mimics remote automation triggers and event payloads to validate complex pipeline configurations without requiring cloud infrastructure.
- Private Infrastructure Automation - Running automation workflows against private internal servers by securely authenticating with enterprise infrastructure instead of relying on public cloud services.
- Workflow Transpilers - Parses workflow definition files to generate and execute equivalent shell scripts within the target container runtime.
- Job Execution Controls - The automation runner provides the ability to run individual workflow tasks by name to isolate and troubleshoot specific logic without triggering the entire automation suite.
- Enterprise Server Authentication - The automation runner facilitates authentication with private enterprise infrastructure by providing hostnames and access tokens to run workflows against internal servers instead of public services.
- Environment Variable Injectors - Injects secrets and configuration parameters into the container runtime to replicate the security context of a remote server.
- Container Engine Configurations - The automation runner supports custom container engine selection by defining socket paths or remote host addresses to ensure compatibility with standard container runtime interfaces.
- Local CI/CD Environments - Running automation workflows directly on your machine to verify logic and configuration changes before pushing code to a remote repository.
- Workflow Debuggers - Isolating and executing specific tasks individually to debug failures without needing to trigger an entire automation suite during development.
- Remote Container Host Configurations - The automation runner allows users to connect to remote container hosts by manually defining host addresses and certificate paths when default configurations are unavailable.
- Workflow Simulation Tools - The automation runner allows users to simulate workflow triggers by passing custom JSON payloads to test how automation logic responds to various event types during development.