jenkinsci/jenkinsfile-runner
Jenkinsfile Runner
Jenkinsfile runner is a continuous integration engine that executes declarative workflows and pipeline scripts directly from the command line or container environments without requiring a persistent master server. It provides terminal-based execution tools for running, testing, and linting pipeline definitions locally, supporting build parameter passing, interactive shell sessions, and source control checkout configurations with authentication for private repositories.
The system supports declarative instance configuration through mounted YAML files, automatic dependency resolution, and on-demand plugin installation to set up required build steps. It packages the execution engine and plugins into container images or standalone executable distributions, allowing custom image building and portable workload execution across different host systems.
Additional capabilities cover data persistence via mounted volumes for logs and execution history, log output customization through configuration files, and custom application package generation from project descriptor files.
Features
- Local Pipeline Execution - Executes continuous integration and deployment pipelines from the command line without requiring a master server architecture.
- Container CI/CD Pipelines - Provides a container-centric execution tool for running continuous integration workflows from the terminal.
- Workflow Execution Engines - Runs predefined build scripts inside a container or command-line environment independently of traditional master servers.
- CI/CD Pipeline Orchestration - Executes continuous integration and deployment workflows defined in code files without needing a persistent orchestration server.
- Containerized Task Execution - Runs continuous integration tasks inside pre-built or custom container images for isolated execution.
- Containerized Build Systems - Packages continuous integration engines and plugins into lightweight containers to run workloads portably across different host systems.
- Containerized Execution Environments - Packages the runtime and execution engine into lightweight container images so workloads run portably across different host systems.
- Command Line Interfaces - Provides a terminal-based command interface to trigger execution runs directly from scripts or developer terminals.
- On-Demand - Installs additional plugins into the execution environment using setup tools or package managers to support required pipeline steps.
- Distribution Package Generators - Builds tailored container images and distributions from project descriptor files to bundle specific dependencies and versions.
- Executable Packaging - Builds a lightweight distribution archive containing the execution engine, required binaries, and dependencies for standalone usage.
- CLI Job Runners - Provides a command-line utility for executing pipeline scripts locally in isolated processes.
- Declarative Configuration Engines - Defines system settings and plugin configurations declaratively by mounting YAML definition files into the container at startup.
- Container Image Packaging - Packages the execution engine and specified plugins into a container image using packaging tools to prepare runnable environments.
- Custom Container Images - Builds tailored container images by installing extra plugins, adding required tools, and baking in pre-configured settings.
- Local CI Testing Tools - Runs pipeline definition scripts from the local command line independently of full server infrastructure for rapid development.
- Pipeline Definitions - Parses pipeline definition scripts as code to validate syntax before running builds.
- Metadata Parameter Passings - Supplies runtime values to parameterized workflows using key-value pairs via command-line switches.
- Pipeline Syntax Linting - Analyzes declarative pipeline syntax for errors without triggering a full execution run.
