[0.0.1] - 2025-11-01

Pipedash First Release

About

Pipedash aggregates CI/CD pipelines from multiple providers into a single desktop interface. Instead of switching between GitHub Actions, Buildkite, and Jenkins dashboards, view everything in one place.

Built with Tauri, Rust, React, and TypeScript.

Why

Most development teams use multiple CI/CD platforms over time. Open source projects often use GitHub Actions, internal services might run on Buildkite, and there's usually some Jenkins instance handling legacy systems. Checking everything means opening multiple tabs and manually refreshing.

This tool pulls pipeline data from different providers and shows it together.

Supported Providers

• GitHub Actions
• Buildkite
• Jenkins

The plugin architecture allows adding more providers.

What It Does

The app polls configured providers and displays pipelines organized by repository and workflow. Background refresh runs every X seconds (configurable per provider). When pipeline status changes, the UI updates automatically.

Main capabilities:

• View pipeline status across multiple providers
• Browse run history with commit info and execution times
• Trigger workflows with parameters dynamically loaded from each provider
• Re-run previous executions with the same parameters
• Cancel running builds
• Multiple instances of the same provider type

When triggering or re-running a workflow, the app fetches available parameters directly from the provider plugin (workflow inputs for GitHub Actions, build parameters for Jenkins, etc.) and displays them in a form.

API tokens are stored in the system keyring (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux). Pipeline data is cached locally in SQLite.