langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #696] [MERGED] add jenkins tool #1108

New Issue
Closed
opened 2026-02-22 17:48:25 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 17:48:25 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/696
Author: @ZombieBlue
Created: 6/15/2025
Status: ✅ Merged
Merged: 6/18/2025
Merged by: @crazywoola

Base: main ← Head: add_jenkins_tool

📝 Commits (3)

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ Organization/jenkins-tool/jenkins-tool.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission

3. Description

Jenkins Tool

A Dify plugin for interacting with Jenkins servers, helping you retrieve build information, view build logs, and trigger new builds.

Features

  • Get Jenkins build information
  • View build Console-output
  • Trigger new builds

Prerequisites

Before using this plugin, you need:

  1. An accessible Jenkins server
  2. Jenkins server credentials (username and API Token)

Configuration

Before using the plugin, you need to configure the following information:

  1. Jenkins server address (e.g., http://your-jenkins-server:8080)
  2. Jenkins username
  3. Jenkins API Token (can be generated in Jenkins user configuration page)

Usage

  1. Install this plugin on the Dify platform
  2. Configure Jenkins server information
  3. Use the provided tools to interact with Jenkins

Notes

  • Ensure the Jenkins server address is accessible
  • Keep your API Token secure and do not share it with others
  • It is recommended to use HTTPS protocol when accessing Jenkins server

Support

For issues or suggestions, please submit feedback through GitHub Issues.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/696 **Author:** [@ZombieBlue](https://github.com/ZombieBlue) **Created:** 6/15/2025 **Status:** ✅ Merged **Merged:** 6/18/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `add_jenkins_tool` --- ### 📝 Commits (3) - [`3f7cbab`](https://github.com/langgenius/dify-plugins/commit/3f7cbab9a8b0ae9e382313cde35a9f0e323fe4e6) add jenkins tool - [`81068ed`](https://github.com/langgenius/dify-plugins/commit/81068ed9d175b8385b08afc6835fa95b763b9a39) remove redundants - [`d1f6105`](https://github.com/langgenius/dify-plugins/commit/d1f6105bead2924ba7f9a9e16ed11c93133a2f4b) remove source code ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `Organization/jenkins-tool/jenkins-tool.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata - **Plugin Author**: Zombieblue - **Plugin Name**: Jenkins-tool - **Repository URL**: https://github.com/ZombieBlue/dify-plugins/tree/add_jenkins_tool ## 2. Submission Type - [x] New plugin submission ## 3. Description # Jenkins Tool A Dify plugin for interacting with Jenkins servers, helping you retrieve build information, view build logs, and trigger new builds. ## Features - Get Jenkins build information - View build Console-output - Trigger new builds ## Prerequisites Before using this plugin, you need: 1. An accessible Jenkins server 2. Jenkins server credentials (username and API Token) ## Configuration Before using the plugin, you need to configure the following information: 1. Jenkins server address (e.g., `http://your-jenkins-server:8080`) 2. Jenkins username 3. Jenkins API Token (can be generated in Jenkins user configuration page) ## Usage 1. Install this plugin on the Dify platform 2. Configure Jenkins server information 3. Use the provided tools to interact with Jenkins ## Notes - Ensure the Jenkins server address is accessible - Keep your API Token secure and do not share it with others - It is recommended to use HTTPS protocol when accessing Jenkins server ## Support For issues or suggestions, please submit feedback through GitHub Issues. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 17:48:25 -05:00
yindo closed this issue 2026-02-22 17:48:26 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1108
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?