Conversation
☁️ Cloudflare Worker Preview Deployed!🔗 https://ks-how-kestra-ships-plugins-docs.kestra-io.workers.dev |
🔦 Lighthouse BenchmarkLast updated: 2026-04-10T20:40:57
Scores (0–100, higher is better)
Core Web Vitals (lower is better)
Legend▲ improved · ▼ regressed · (blank) no significant change |
Visual Changes DetectedMake sure changes are expected and review the Playwright report for details. Playwright report artifact: https://github.com/kestra-io/docs/actions/runs/24262399880/artifacts/6379314859 To accept the updated visuals, click Accept, select the PR branch, and run the workflow. |
| --- | ||
|
|
||
| The Plugins & Integrations team at Kestra is responsible for the 1200+ plugins that connect Kestra to the rest of the data and cloud ecosystem. [AWS](/plugins/plugin-aws), [GCP](/plugins/plugin-gcp), [Azure](/plugins/plugin-azure), [Snowflake](/plugins/plugin-jdbc-snowflake), [Kafka](/plugins/plugin-kafka), [dbt](/plugins/plugin-dbt), [Airbyte](/plugins/plugin-airbyte), and a few hundred more. Every release, every regression, every compatibility check across all of them falls to us. | ||
|
|
There was a problem hiding this comment.
@elliotgunn Let's wait my new flow to implement new features & fixes through calls to Claude Code GitHub Actions to automate our all workflow and also talk about how we automate and accelerate such a volume of plugins' maintenance & evolving. So that the post impact will be even more bigger.
Or maybe it can be a dedicated blog post actually? Because it involves a lot of skills & agents we're writing. I'll dig it up once my talk / flow will be ready :) What do you think?
| @@ -0,0 +1,63 @@ | |||
| --- | |||
| title: "How Kestra Ships and Maintains 1200+ Plugins" | |||
There was a problem hiding this comment.
No mention about dogfooding? 🐶
|
|
||
| `weekend_compatibility_check` runs every Saturday. It takes the entire plugin library and runs it against the latest `develop` branch of Kestra core. The results land in Slack before the week starts. | ||
|
|
||
| The fifth flow, `weekly_released_plugins`, compiles a digest of everything that shipped: new features, bug fixes, version bumps. It posts automatically to [Slack](/plugins/plugin-slack) and our [Notion](/plugins/plugin-notion) database. The team gets a summary without anyone writing one. |
There was a problem hiding this comment.
We should mention it helps people outside Plugins Team, so other teams from engineering, product, customer success, marketing and sales teams to have a vision about what we're doing and delivering :)
|
|
||
| ## The floor we didn't know we were missing | ||
|
|
||
| Before we had these flows, a release that ran smoothly felt like a success. Now, a release that runs smoothly is the floor, not the ceiling. We get focus on the important questions that require human judgment. Why did this compatibility check fail? What changed in this dependency? Why is this plugin failing on the develop branch but not on main? |
There was a problem hiding this comment.
Plugins don't have "develop" branches
2 participants
still needs: