Enable Google Gemini in Jenkins Explain Error Plugin for Faster Build Error Analysis

The Jenkins Explain Error Plugin now supports Google Gemini, allowing users to configure the plugin with Gemini's API key and endpoint to leverage AI-powered error analysis directly within Jenkins builds.

DevOps Engineer
DevOps Engineer
DevOps Engineer
Enable Google Gemini in Jenkins Explain Error Plugin for Faster Build Error Analysis

Last week I released the Jenkins Explain Error Plugin, designed to help Jenkins users analyze and resolve build errors more quickly using built-in AI.

Some users requested support for the Google Gemini model because their organizations only use Google AI services.

Today I’m pleased to announce that the plugin now supports Google Gemini!

Plugin updates

Added support for the Google Gemini model

Improved documentation and added example video

How to use Google Gemini

Before you start, make sure the plugin is updated to the latest version via the Jenkins Plugin Manager.

After updating, go to Manage Jenkins → Configure System and locate the Explain Error Plugin Configuration section. Set the model to Google Gemini and provide the corresponding API URL and key.

Explain Error Plugin Configuration

Click Test Configuration to verify that your Google Gemini API key, URL, and model are correctly entered and reachable.

Plugin example video

I recorded a short video demonstrating how to use the Explain Error Plugin with AI for error analysis in Jenkins.

Conclusion

If you encounter any issues or have suggestions, feel free to open an issue on GitHub or leave a comment.

Repository: jenkinsci/explain-error-plugin

Please give the project a star to show your support!

References

https://github.com/jenkinsci/explain-error-plugin

CI/CDAIJenkinsGoogle GeminiExplain Error Plugin
DevOps Engineer
Written by

DevOps Engineer

DevOps engineer, Pythonista and FOSS contributor. Created cpp-linter, commit-check, etc.; contributed to PyPA.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.