|
| 1 | +# PipelineX Roadmap |
| 2 | + |
| 3 | +> Last updated: February 2026 |
| 4 | +
|
| 5 | +--- |
| 6 | + |
| 7 | +## Completed Phases |
| 8 | + |
| 9 | +### ✅ v1.0.x — Foundation (Complete) |
| 10 | + |
| 11 | +- Rust-based CLI (`analyze`, `optimize`, `diff`, `cost`, `graph`) |
| 12 | +- Multi-platform pipeline parsing: GitHub Actions, GitLab CI, Jenkins, CircleCI, Bitbucket Pipelines, Azure Pipelines, AWS CodePipeline, Buildkite |
| 13 | +- Core antipattern detectors: missing caches, serial bottlenecks, false dependencies, Docker inefficiencies |
| 14 | +- Auto-generation of optimized pipeline configs |
| 15 | +- Multiple output formats: plain text (coloured), JSON, SARIF (GitHub Code Scanning) |
| 16 | +- Critical path analysis with estimated savings per finding |
| 17 | +- Confidence scoring and auto-fixable detection |
| 18 | + |
| 19 | +### ✅ v1.x — Intelligence & Ecosystem (Complete) |
| 20 | + |
| 21 | +- 12 antipattern detectors (caches, serial bottlenecks, false dependencies, flaky tests, path filtering, matrix bloat, Docker layer caching, and more) |
| 22 | +- `pipelinex flaky` — flaky test detection from test result files |
| 23 | +- `pipelinex select-tests` — smart test selection based on changed files |
| 24 | +- `pipelinex history` — historical run data analysis from GitHub API |
| 25 | +- `pipelinex cost` — cost estimation with runs-per-month projection |
| 26 | +- DAG visualisation (`pipelinex graph`) |
| 27 | +- One-line install script (`install.sh`) |
| 28 | +- Docker image for zero-install usage |
| 29 | +- GitHub Actions integration with SARIF upload |
| 30 | +- Pre-commit hook support |
| 31 | +- VS Code extension with inline diagnostics |
| 32 | +- Makefile with developer workflow tasks |
| 33 | + |
| 34 | +### ✅ v2.0.x — Platform & Dashboard (Complete) |
| 35 | + |
| 36 | +- Interactive web dashboard with dark mode |
| 37 | +- DAG explorer with visual pipeline graph |
| 38 | +- Trends and cost centre analysis views |
| 39 | +- HTML report output format (interactive, shareable) |
| 40 | +- REST API for programmatic access |
| 41 | +- Self-hosted deployment via `docker-compose.selfhost.yml` |
| 42 | +- Helm chart for Kubernetes deployment (`deploy/helm/pipelinex-dashboard`) |
| 43 | +- `.pipelinex/` project-level configuration directory |
| 44 | +- Comprehensive documentation (QUICKSTART, INTEGRATIONS, SELF_HOSTING, REST_API, VS_CODE_EXTENSION) |
| 45 | +- Examples directory with integration samples |
| 46 | + |
| 47 | +### ✅ v2.1.x — Polish & Reliability (Complete) |
| 48 | + |
| 49 | +- Stability fixes and edge-case handling across all 8 CI parsers |
| 50 | +- Improved confidence scoring accuracy |
| 51 | +- Release checklist and publishing workflow |
| 52 | +- Implementation verification documentation |
| 53 | + |
| 54 | +--- |
| 55 | + |
| 56 | +## Upcoming Phases |
| 57 | + |
| 58 | +### 🔜 v2.2.x — Usability & Adoption (Q2 2026) |
| 59 | + |
| 60 | +#### Installation & Onboarding |
| 61 | + |
| 62 | +- **Package manager distribution**: `brew install pipelinex`, `cargo install pipelinex-cli` on crates.io, `npm`/`npx` wrapper, `.deb`/`.rpm` packages, and Windows `winget`/`scoop` support |
| 63 | +- **`pipelinex init`**: Interactive setup wizard that auto-detects CI platform from repo structure, generates a `.pipelinex/config.toml`, and runs the first analysis with guided walkthrough |
| 64 | +- **`pipelinex doctor`**: Diagnostic command that checks CI config syntax, validates platform detection, and reports parser coverage gaps in one pass |
| 65 | + |
| 66 | +#### Day-to-Day Workflow |
| 67 | + |
| 68 | +- **`--watch` mode**: File-watching mode that re-analyses pipeline configs on save — instant feedback during CI config editing |
| 69 | +- **PR comment bot**: GitHub App / GitLab integration that posts analysis results as inline PR comments when CI configs change — shows findings, estimated savings, and one-click "apply optimized config" |
| 70 | +- **`pipelinex explain <finding-id>`**: Deep-dive command that explains a specific finding with real-world context, benchmarks from similar projects, and step-by-step remediation instructions |
| 71 | +- **Monorepo support**: Analyse multiple pipeline files across a monorepo with per-package cost attribution and aggregated reporting |
| 72 | +- **Config validation mode**: `pipelinex lint` that checks CI configs for syntax errors, deprecated features, and platform-specific gotchas before pushing — a "CI config linter" |
| 73 | + |
| 74 | +#### Dashboard Enhancements |
| 75 | + |
| 76 | +- **Team/org views**: Multi-repo dashboard aggregating pipeline health, cost trends, and optimisation adoption across an entire organisation |
| 77 | +- **Before/after comparison**: Side-by-side visualisation of pipeline DAGs before and after optimisation — animated transition showing parallelisation gains |
| 78 | +- **Notification system**: Webhook, Slack, and email alerts when pipeline performance regresses (e.g., build time increases by >20% over baseline) |
| 79 | +- **Embeddable widgets**: Iframe-ready charts for CI health that teams can embed in internal wikis or Notion pages |
| 80 | + |
| 81 | +#### CLI & Output |
| 82 | + |
| 83 | +- **Shell completions**: Auto-generated completions for Bash, Zsh, Fish, and PowerShell |
| 84 | +- **Markdown output format**: Clean markdown reports suitable for pasting into GitHub issues, PRs, or wiki pages |
| 85 | +- **`pipelinex compare <config-a> <config-b>`**: Diff two pipeline configs with annotated optimisation delta and estimated time/cost difference |
| 86 | + |
| 87 | +--- |
| 88 | + |
| 89 | +### 🛡️ v2.3.x — Security & Trust (Q3 2026) |
| 90 | + |
| 91 | +#### Pipeline Security Analysis |
| 92 | + |
| 93 | +- **Secret exposure detection**: Flag hardcoded secrets, tokens, and credentials in pipeline configs (environment variables, inline scripts, step arguments) |
| 94 | +- **Overprivileged permissions audit**: Detect GitHub Actions workflows with `permissions: write-all` or overly broad token scopes — suggest minimal required permissions per job |
| 95 | +- **Supply chain risk scoring**: Analyse third-party actions/orbs/images for pinning practices (tag vs SHA), popularity, maintenance status, and known vulnerabilities |
| 96 | +- **Untrusted input injection**: Detect patterns where `github.event` fields, PR titles, or branch names flow into `run:` steps unsanitised — a major GitHub Actions attack vector |
| 97 | +- **Self-hosted runner risk assessment**: Flag workflows that run on self-hosted runners without appropriate isolation, network restrictions, or ephemeral configuration |
| 98 | + |
| 99 | +#### Compliance & Audit |
| 100 | + |
| 101 | +- **Signed analysis reports**: Cryptographically signed JSON/SARIF output so teams can prove an analysis was run and results weren't tampered with |
| 102 | +- **Pipeline change audit trail**: Track which optimisations were applied, when, and by whom — with before/after snapshots stored in `.pipelinex/history/` |
| 103 | +- **Compliance policies**: Define organisational rules in TOML/YAML (e.g., "all workflows must pin actions by SHA", "no workflows may use `ubuntu-latest`", "cache must be configured for npm/yarn") — `pipelinex policy check` enforces them |
| 104 | +- **SBOM for CI**: Generate a "CI Bill of Materials" listing every action, orb, image, and tool version used across all pipelines |
| 105 | + |
| 106 | +#### Data Protection |
| 107 | + |
| 108 | +- **Offline-only mode**: Guaranteed no network calls — all analysis runs locally with no telemetry, API calls, or external lookups (important for air-gapped/regulated environments) |
| 109 | +- **Redacted reports**: Auto-strip sensitive values (repo names, secret names, internal URLs) from reports before sharing externally |
| 110 | +- **RBAC for dashboard**: Role-based access control for the self-hosted dashboard — admin, editor, viewer roles with SSO integration (OIDC, SAML) |
| 111 | + |
| 112 | +--- |
| 113 | + |
| 114 | +### ✨ v3.0.x — Woo Factor & Intelligence (Q4 2026) |
| 115 | + |
| 116 | +#### AI-Powered Analysis |
| 117 | + |
| 118 | +- **LLM-powered optimisation explanations**: Natural language explanations of findings and fixes — *"Your test job waits for lint to finish, but they don't share any artifacts. Running them in parallel would save ~8 minutes per run and $43/month."* |
| 119 | +- **AI config generation**: Describe what your pipeline should do in plain English, get an optimised CI config generated — *"Build a Node.js app, run tests in parallel across Node 18 and 20, deploy to AWS on main branch"* |
| 120 | +- **Predictive build time**: ML model trained on historical run data that predicts build time for a given PR before it even runs — *"This PR touches 3 test files, estimated CI time: 12 min (vs 31 min baseline)"* |
| 121 | +- **Anomaly detection**: Automatically flag pipeline runs that are significantly slower than usual — distinguish between legitimate slowdowns (new tests added) and regressions (cache miss, flaky infra) |
| 122 | + |
| 123 | +#### Visualisation & Impact |
| 124 | + |
| 125 | +- **Live pipeline monitor**: Real-time dashboard showing active CI runs across all repos with live progress bars, step-level timing, and instant bottleneck highlighting — a "mission control" for your CI fleet |
| 126 | +- **"Pipeline Health Score" badge**: Embeddable shields.io-style badge for READMEs (`PipelineX Score: A+ | 94% optimised`) — gamification that drives adoption across open-source projects |
| 127 | +- **Cost leaderboard**: Org-wide ranking of repos by CI cost efficiency — *"Team Backend saved $2,400/month after applying PipelineX suggestions. Team Frontend: $890 potential savings remaining."* — turns optimisation into a friendly competition |
| 128 | +- **Interactive "what-if" simulator**: Browser-based tool where you can drag jobs around the DAG, add/remove dependencies, toggle caching on/off, and instantly see the projected impact on build time and cost — no actual config changes needed |
| 129 | +- **Time-lapse replay**: Animate how a pipeline's performance has evolved over weeks/months — watch the DAG optimise in fast-forward as fixes are applied |
| 130 | + |
| 131 | +#### Ecosystem Expansion |
| 132 | + |
| 133 | +- **Tekton and Argo Workflows support**: Kubernetes-native CI/CD systems as first-class analysis targets |
| 134 | +- **Drone CI and Woodpecker CI support**: Lightweight CI systems popular in self-hosted setups |
| 135 | +- **MCP (Model Context Protocol) server**: Expose PipelineX as an MCP tool so AI coding assistants can analyse and optimise pipelines conversationally |
| 136 | +- **GitHub Marketplace App**: One-click install GitHub App that automatically analyses PRs touching CI configs and posts optimisation suggestions |
| 137 | +- **Terraform CI module**: IaC module that provisions PipelineX dashboard alongside your CI infrastructure |
| 138 | +- **JetBrains IDE plugin**: IntelliJ/GoLand/WebStorm plugin with inline pipeline analysis, DAG preview, and quick-fix actions |
| 139 | + |
| 140 | +#### Developer Experience |
| 141 | + |
| 142 | +- **Online playground**: Browser-based "paste your CI config" analyser using a WASM build — zero install, instant demo, shareable results via URL |
| 143 | +- **`pipelinex benchmark`**: Run your pipeline N times and produce statistical analysis (p50, p95, p99 build times, variance, flakiness rate) with visualisation |
| 144 | +- **Plugin system**: User-extensible antipattern detectors — write custom rules in Rust or WASM, distribute via a plugin registry |
| 145 | +- **VS Code extension v2**: Inline DAG preview in the editor, hover cards with cost estimates per job, and "optimise this file" code action |
| 146 | + |
| 147 | +--- |
| 148 | + |
| 149 | +## Long-Term Vision (2027+) |
| 150 | + |
| 151 | +- **Cross-pipeline dependency analysis**: Detect bottlenecks that span multiple pipelines (e.g., a deploy pipeline waiting on a build pipeline that's slow because of a test pipeline) |
| 152 | +- **Automatic PR generation**: When PipelineX finds optimisations, it opens a PR with the optimised config, a summary of changes, and projected savings — fully automated |
| 153 | +- **PipelineX Cloud**: Hosted SaaS with org management, historical analytics, SSO, and managed dashboards — no self-hosting required |
| 154 | +- **CI provider cost API integration**: Pull actual billing data from GitHub Actions, GitLab CI, CircleCI, and Buildkite to show real (not estimated) cost savings |
| 155 | +- **FinOps dashboard**: Dedicated cost management view with budget alerts, per-team chargeback, and month-over-month spend tracking across all CI providers |
| 156 | +- **Pipeline-as-Code testing**: `pipelinex test` that simulates a pipeline run locally (mocked steps) to validate config changes before pushing — a "unit test for your CI" |
| 157 | + |
| 158 | +--- |
| 159 | + |
| 160 | +## How to Contribute |
| 161 | + |
| 162 | +We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for details. |
| 163 | + |
| 164 | +**High-impact areas right now:** |
| 165 | + |
| 166 | +- 🔍 Adding antipattern detectors for new CI bottleneck patterns |
| 167 | +- 🔌 Expanding CI platform parser coverage (Tekton, Argo, Drone) |
| 168 | +- 🔐 Pipeline security analysis rules (secret exposure, supply chain risks) |
| 169 | +- 📊 Dashboard visualisation improvements |
| 170 | +- 📚 Documentation, tutorials, and example configs |
| 171 | +- 🧪 Test fixtures for edge cases across all 8 CI platforms |
| 172 | + |
| 173 | +Report bugs or request features via [GitHub Issues](https://github.com/mackeh/PipelineX/issues). |
0 commit comments