Can Cockpit trigger actions in Jenkins, and Jenkins in Cockpit?

Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it.

Do I need to write code to integrate Cockpit and Jenkins?

No. Cockpit-to-Jenkins automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.

Cockpit + Jenkins Integration

Connect Cockpit and Jenkins to automate developer tools work — trigger in one app, run actions in the other, wired in minutes.

Example: when Jenkins's "Watch New Builds" fires, WEXTL can "Create Collection" in Cockpit. Cockpit has 11 actions (including Create Collection, Create Entry, and Delete Entry); Jenkins has 64 actions (including Add Job to View, Build Job, and Build Job With Parameters).

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

Jenkins triggersCockpit actions

Jenkins workflow triggers

Cockpit workflow actions

Frequently asked questions

Common questions about connecting Cockpit and Jenkins.

Connect your Cockpit and Jenkins accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.

CockpitBrowse all Cockpit triggers, actions, and integrations.

JenkinsBrowse all Jenkins triggers, actions, and integrations.

Cockpit + Jenkins Integration

Frequently asked questions

How do I connect Cockpit and Jenkins?

What can I automate between Cockpit and Jenkins?

Can Cockpit trigger actions in Jenkins, and Jenkins in Cockpit?

Do I need to write code to integrate Cockpit and Jenkins?

Explore Cockpit and Jenkins, or get started

Cockpit + Jenkins Integration

Frequently asked questions

How do I connect Cockpit and Jenkins?

What can I automate between Cockpit and Jenkins?

Can Cockpit trigger actions in Jenkins, and Jenkins in Cockpit?

Do I need to write code to integrate Cockpit and Jenkins?

Explore Cockpit and Jenkins, or get started