Pipeline Marketplace
How to quickly start a pipeline from pre-configured Starter Workflows
The Pipeline Marketplace is a Starter Workflow gallery with pre-configured CI/CD scenarios ready to use. Select a repository, click a card, and the Workflow file editor opens with the template content pre-filled.
How to Access
Marketplace button at the top of the Pipelines page
When a workspace has no Workflows yet, the pipeline page redirects to the marketplace automatically
Direct URL: /\{workspace-slug\}/pipelines/marketplace
Usage Flow
Enter the marketplace.
Choose a category chip at the top (All / CI / Build / Testing / Deployments / Release / Code Scanning / Quality / Workflow Pattern).
Select the target Repository from the dropdown on the right (required).
Click the Configure button on the Starter Workflow card you want.
The editor opens at .collabops/workflows/\{template_name\}.yml with the template content pre-filled.
Modify as needed and commit to register the Workflow.
The Configure button is disabled until a Repository is selected, showing a "Select a repository first" hint. The marketplace creates the Workflow file in a specific repository, so a target is required.
Starting from Scratch (Blank Workflow)
To start from an empty Workflow instead, click the Blank Workflow button at the top-right of the gallery. This creates an empty .collabops/workflows/pipeline.yml.
Categories
| Category | Description |
|---|---|
| CI | Per-language and per-framework build, test, and lint CI |
| Build | Docker image and artifact builds (multi-stage, multi-platform, monorepo, Java, …) |
| Testing | Test-focused — E2E, matrix, sharding, coverage |
| Deployments | Deploy automation — AWS/GCP/Vercel/Firebase/Fly.io/Supabase/npm/SSH |
| Release | Release gates — tag release, pre-merge validation, scheduled cleanup |
| Code Scanning | Security scans — SAST and secret detection |
| Quality | Code quality analysis — Lint and SonarQube |
| Workflow Pattern | Multi-job orchestration patterns — monorepo, scheduled, artifact handoff |
Available Starter Workflows
CI (21)
| Name | Description | System Templates Used |
|---|---|---|
| Basic CI | Lint, test, and build pipeline for Node.js projects | checkout |
| Docker Compose Test | Integration tests with Docker Compose services (DB, Redis) | checkout |
| Python CI | Lint (ruff, mypy) and test (pytest) pipeline for Python projects | checkout |
| Go CI | Build, test, and vet pipeline for Go projects | checkout |
| Java Maven CI | Build and test pipeline for Java projects with Maven | checkout |
| TypeScript CI | Type-check and build TypeScript projects | checkout |
| NestJS API CI | Lint, test, and build NestJS applications | checkout |
| Next.js Build CI | Type-check, lint, and build Next.js applications | checkout |
| React (Vite) CI | Lint, test, and build Vite-based React applications | checkout |
| Vue (Vite) CI | Lint, test, and build Vite-based Vue applications | checkout |
| SvelteKit CI | Check, test, and build SvelteKit applications | checkout |
| Angular CI | Test and build Angular applications | checkout |
| Rust (Cargo) CI | Format, clippy, test, and build Rust projects | checkout |
| Ruby (RSpec) CI | Bundle install and run RSpec test suite | checkout |
| PHP (Laravel) CI | Composer install and run PHPUnit tests for Laravel apps | checkout |
| .NET CI | Restore, test, and build .NET solutions | checkout |
| Kotlin (Gradle) CI | Gradle build and test for Kotlin/JVM projects | checkout |
| Scala (sbt) CI | sbt test and package for Scala projects | checkout |
| Swift Package CI | Test Swift packages via swift test | checkout |
| Django (pytest) CI | pip install and run pytest for Django projects | checkout |
| FastAPI (pytest) CI | pip install and run pytest for FastAPI services | checkout |
Build (15)
| Name | Description | System Templates Used |
|---|---|---|
| Cache + Build | Node.js build with dependency caching for faster CI runs | checkout, cache |
| Docker Build & Push | Build a Docker image and push to an internal container registry | checkout, docker-login, docker-build-push |
| Docker Multi-stage Build | Build a multi-stage Docker image and push to an internal registry | checkout, docker-login, docker-build-push |
| Microservice Monorepo Build | Build each service in a monorepo into its own image in parallel | checkout, docker-login, docker-build-push |
| Docker Buildx (multi-platform) | Build multi-architecture images (linux/amd64 + linux/arm64) | checkout, docker-login, docker-build-push |
| Nightly Base Image Build | Rebuild and push a base image on a nightly schedule | checkout, docker-login, docker-build-push |
| Monorepo (pnpm workspace) | Install, build, and lint all packages in a pnpm workspace | checkout |
| Java Spring Boot (JAR · onprem) | JDK 17 + Maven 3.9 + Spring Boot 3.x executable JAR with private Nexus mirror | checkout, cache, upload-artifact |
| Java Spring Boot (JDK 8 · onprem) | JDK 8 + Maven + Spring Boot 2.7 executable JAR — legacy compatibility | checkout, cache, upload-artifact |
| Java Spring Boot (JDK 11 · onprem) | JDK 11 + Maven + Spring Boot 2.7 executable JAR | checkout, cache, upload-artifact |
| Java Spring Boot (JDK 21 · onprem) | JDK 21 + Maven + Spring Boot 3.x executable JAR with Virtual Threads support | checkout, cache, upload-artifact |
| Java Spring Boot (Gradle · onprem) | JDK 17 + Gradle 8 (Groovy DSL) + Spring Boot 3.x executable JAR with private Nexus mirror | checkout, cache, upload-artifact |
| Java Spring Boot (Multi-module · onprem) | Maven multi-module (api/domain/common) reactor build — JDK 17 + Spring Boot 3.x | checkout, cache, upload-artifact |
| Java Spring Boot (Harbor image · onprem) | Spring Boot container image build + private Harbor registry push with robot account | checkout, docker-build-push |
| Docker Hub Build & Push | Authenticate to Docker Hub, then build and push a Docker image | checkout, docker-login, docker-build-push |
Testing (5)
| Name | Description | System Templates Used |
|---|---|---|
| E2E (Playwright) | Run Playwright end-to-end tests against a built application | checkout, upload-artifact |
| E2E (Cypress) | Run Cypress end-to-end tests headlessly | checkout, upload-artifact |
| Matrix: Node.js Versions | Run the same test suite against Node.js 18, 20, and 22 in parallel | checkout |
| Parallel Test Shards | Split Jest test suite into 4 shards and run them in parallel | checkout |
| Test Coverage Report | Generate a coverage report and publish as an artifact | checkout, upload-artifact |
Deployments (17)
| Name | Description | System Templates Used |
|---|---|---|
| GCP Docker Deploy | Build, push to Artifact Registry, and deploy to GKE | checkout, gcloud-auth, gcloud-docker-auth, docker-build-push, gcloud-setup, slack-notify |
| AWS Docker Deploy | Build, push to ECR, and deploy to EKS | checkout, aws-auth, aws-ecr-auth, docker-build-push, aws-eks-setup, slack-notify |
| Vercel Deploy | Build and deploy to Vercel (Preview or Production) | checkout, vercel-deploy, slack-notify |
| Firebase Deploy | Build and deploy to Firebase Hosting/Functions | checkout, firebase-deploy |
| Fly.io Deploy | Deploy applications to Fly.io using flyctl | checkout, fly-deploy |
| Supabase Deploy | Run DB migrations and deploy Edge Functions to Supabase | checkout, supabase-migration, supabase-functions-deploy |
| npm Publish | Test and publish npm packages on tag push with provenance | checkout, npm-publish |
| SSH Deploy | Upload files via SSH and restart Docker Compose on remote host | checkout, scp-upload, ssh-exec |
| Java Spring Boot (Nexus publish · onprem) | mvn deploy to private Nexus — snapshot/release routing via distributionManagement | checkout |
| GCP Cloud Run Deploy | Build image, push to Artifact Registry, deploy to Cloud Run | checkout, gcloud-auth, gcloud-docker-auth, docker-build-push |
| AWS ECS Deploy | Build image, push to ECR, and update an ECS service | checkout, aws-auth, aws-ecr-auth, docker-build-push |
| Firebase Hosting Deploy | Build and deploy only the Hosting target to Firebase | checkout, firebase-deploy |
| npm Publish on Tag | Publish the package to npm when a semver tag is pushed | checkout, npm-publish |
| Java Spring Boot (JAR · systemd VM · onprem) | Spring Boot executable JAR build + scp/ssh deploy to bare-metal VM with systemd unit, atomic symlink swap, and previous-release rollback | checkout, scp-upload, ssh-exec |
| Java Spring Boot (WAR · external Tomcat · onprem) | Spring Boot WAR build + SSH deploy to external Tomcat with parallel deployment | checkout, scp-upload, ssh-exec |
| Java Spring Boot (Multi-env promote · onprem) | Build once + promote artifact dev/stg auto, prd manual (workflow_dispatch) | checkout, upload-artifact, download-artifact, scp-upload, ssh-exec |
| Vercel Preview Deploy | Build and deploy a preview environment to Vercel on every change-request | checkout, vercel-deploy |
Release (4)
| Name | Description | System Templates Used |
|---|---|---|
| Tag Release Pipeline | On tag push, build release artifacts and upload them for downstream jobs | checkout, upload-artifact |
| Scheduled Cleanup | Nightly maintenance job — can be customized for cache pruning, log rotation, etc. | checkout |
| Pre-merge Validation | Run full SAST + secret-detect + tests on every change-request before merge | checkout, sast-scan, secret-detect |
| Conditional Deploy on Tag | On tag push, build image and push to internal registry (customize target environment) | checkout, docker-login, docker-build-push |
Code Scanning (6)
| Name | Description | System Templates Used |
|---|---|---|
| Security Scan | SAST analysis (Semgrep) and secret detection (Gitleaks) | checkout, sast-scan, secret-detect, slack-notify |
| Full Security Scan | Lint + SAST + secret detection with weekly scheduled scan | checkout, lint, sast-scan, secret-detect, slack-notify |
| Security Scan (Essentials) | SAST + secret detection without external notification — works in airgapped environments | checkout, sast-scan, secret-detect |
| Pre-commit Checks | Run ESLint + Prettier on every change-request before merge | checkout |
| SAST Only | Run static application security testing (Semgrep) without extras | checkout, sast-scan |
| Secret Detection Only | Scan for accidentally committed secrets on every push | checkout, secret-detect |
Quality (3)
| Name | Description | System Templates Used |
|---|---|---|
| Lint Only | Multi-language code linting with MegaLinter on change requests | checkout, lint |
| SonarQube Scan | Upload code quality and security analysis to your SonarQube server on push and change requests | checkout, sonar-scan |
| SonarQube Quality Gate | Block change requests when the SonarQube quality gate fails | checkout, sonar-scan |
Workflow Pattern (3)
| Name | Description | System Templates Used |
|---|---|---|
| Monorepo Pipeline | Parallel frontend/backend build, test, and deploy for monorepo projects | checkout |
| Scheduled Pipeline | Nightly build with lint, test, coverage, and Slack notification | checkout, slack-notify |
| Artifact Pipeline | Multi-job pipeline (build → test → pack) using upload/download-artifact for inter-job file handoff | checkout, upload-artifact, cache, download-artifact, docker-login, docker-build-push |
After Creation
After committing the Workflow file, you usually need to configure the following for it to run correctly:
Register Secrets — Deploy credentials, API tokens, etc. (e.g., AWS_ACCESS_KEY_ID, VERCEL_TOKEN). See Secrets & Variables.
Connect SSH Keys — The checkout template accesses repositories over SSH. See SSH Key Management.
Adjust Triggers — Modify branches, paths, etc. in the template to match your project policy. See Triggers.
Next Steps
CI/CD Overview — Understand the full Workflow YAML structure
System Templates — Built-in templates used by Starter Workflows
Workspace Templates — Create custom templates for your team