Skip to main content
  1. Posts/

Jenkins Explain Error Plugin Now Supports Ollama! 🤖

·421 words·2 mins· ·
Xianpeng Shen
Author
Xianpeng Shen
DevOps & Build Engineer | Python Enthusiast | Open Source Maintainer
Table of Contents

I previously released the Jenkins Explain Error Plugin, which allows Jenkins users to analyze and resolve build errors faster with the help of AI.

Recently, some friends asked: Can it support local models, such as Ollama?

The answer is: It’s happening!

Today, I’m excited to announce: The Explain Error Plugin now supports Ollama models! 🎉

Supports Ollama

The Power of the Community
#

This update, in fact, wouldn’t have been possible without the community’s drive. While I was still validating user needs, a Jenkins community member directly contributed a PR—introducing langchain4j, enabling the plugin to extend support for more models, including Ollama.

Even more surprisingly, this contributor turned out to be the co-founder and CEO of a Dutch company. This once again made me feel the charm of the open-source community: Needs + Contributions = Better Tools.

Configuration in future versions will also be simpler; users will no longer need to fill in complex API URLs, they can just select the model and use it.

New Version Update Highlights

  • Added support for Ollama models
  • Introduced langchain4j, making it easier to extend more AI models in the future
  • Simpler configuration, no need to manually enter API addresses

How to Enable Ollama
#

  1. Upgrade to the latest version of Explain Error Plugin in Jenkins Plugin Manager.
  2. Open: Manage Jenkins → Configure System → Explain Error Plugin Configuration
  3. Select Ollama from the dropdown, fill in the corresponding API address (required for local models) and key.
    Explain Error Plugin Configuration
  4. Click Test Configuration to confirm the connection is normal, then you can start using it!

Why Is It Worth Trying?
#

  • Local model support: No worries about cloud data leakage
  • One-click build error analysis: Quickly pinpoint issues with AI, saving troubleshooting time
  • Community-driven: Features stem from real needs and contributions

Whether you are an individual developer or an enterprise team, the Explain Error Plugin can make your CI/CD process smarter and more efficient.

Finally
#

If you have any thoughts or questions during use, feel free to:

  • Submit an issue on GitHub
  • Leave a comment in the comments section

If you find this plugin helpful, please give it a Star ⭐️!

This will not only help more Jenkins users discover it but also motivate me to continue optimizing and expanding its features.

If you find this article helpful, feel free to share it with your friends who use Jenkins.


When reprinting articles from this site, please credit the author and source, and do not use for any commercial purposes. Welcome to follow the official WeChat account “DevOps Engineer”.

Related

Jenkins Explain Error Plugin Now Supports Google Gemini! 🤖
·310 words·1 min
This article introduces a new feature of the Jenkins Explain Error Plugin that supports for Google Gemini model for error analysis. It provides configuration methods and an example video.
Jenkins Plugin Center Didn't Have an AI Plugin Yet? I Wrote One! 🤖
·751 words·2 mins
Introducing my first Jenkins plugin: Explain Error Plugin. It automatically analyzes build failure log information and generates readable error explanations, helping developers locate and solve problems faster.
Jenkins Linux agent configuration
·298 words·2 mins
Provides a step-by-step guide on how to configure a Jenkins Linux agent, including setting up the Java runtime, creating the node, and troubleshooting common issues.
Jenkins Windows agent configuration
·544 words·3 mins
Provides a step-by-step guide on how to configure a Jenkins Windows agent, including setting up the Java runtime, creating the node, and troubleshooting common issues.
Jenkins Multibranch Pipeline
·405 words·2 mins
Discusses the use of Jenkins Multibranch Pipeline to manage multiple branches in a project, enabling parallel builds for pull requests and efficient code review processes.
How to Fix Shields.io Badges Not Displaying in Jenkins
·218 words·2 mins
How to temporarily fix it via the Script Console, and how to make it permanent by modifying Jenkins startup parameters. This method is suitable for internal Jenkins environments and has been tested on modern Jenkins installations.