feat: add AWS Bedrock provider

[lidiams96]

Summary

Add AWS Bedrock as a new AI provider, enabling models like Claude 3.5 Sonnet, Llama 3, Amazon Nova, and other Bedrock-supported models.

Motivation

AWS Bedrock is widely used in enterprise environments running Jenkins on AWS infrastructure. Adding Bedrock support allows users to:

• Use models like Claude 3.5 Sonnet for high-quality error analysis
• Leverage EU cross-region inference profiles for data residency compliance
• Authenticate using the default AWS credential chain (instance profiles, environment variables) — no API keys needed

Changes

File	Description
pom.xml	Added langchain4j-bedrock dependency
BedrockProvider.java	Provider implementation with region and model configuration
config.jelly	Jenkins UI configuration form with region and model fields
help-region.html	Help text for the region field
help-model.html	Help text with model ID examples
ProviderTest.java	Added validation tests for null/empty model

Configuration

• Region: AWS region (e.g., eu-west-1, us-east-1). Optional — falls back to default AWS SDK region resolution.
• Model: Bedrock model ID or inference profile (e.g., eu.anthropic.claude-3-5-sonnet-20240620-v1:0).
• Authentication: Uses the default AWS credential chain. No API key field needed.

Testing

• Validation tests for null/empty model added to ProviderTest.java
• Follows the same pattern as existing Ollama, OpenAI, and Gemini providers

[Copilot]

Pull request overview

Adds AWS Bedrock as a new BaseAIProvider implementation so Jenkins users can run error analysis against Bedrock-hosted models (via the default AWS credential/region resolution chain).

Changes:

• Introduces BedrockProvider with region + model configuration and a “Test Configuration” UI action.
• Adds Jenkins UI resources (config + help) for the new provider.
• Extends provider validation tests and adds the Bedrock LangChain4j dependency.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
pom.xml	Adds langchain4j-bedrock dependency needed for Bedrock integration.
src/main/java/io/jenkins/plugins/explain_error/provider/BedrockProvider.java	Implements the Bedrock-backed provider, including region handling and test endpoint.
src/main/resources/io/jenkins/plugins/explain_error/provider/BedrockProvider/config.jelly	Adds Jenkins configuration form fields for region/model and a test button.
src/main/resources/io/jenkins/plugins/explain_error/provider/BedrockProvider/help-region.html	Documents how region selection works (including default AWS resolution).
src/main/resources/io/jenkins/plugins/explain_error/provider/BedrockProvider/help-model.html	Documents expected model IDs and links to Bedrock model list.
src/test/java/io/jenkins/plugins/explain_error/provider/ProviderTest.java	Adds null/empty model validation tests for Bedrock provider.

[shenxianpeng]

@lidiams96 Thanks for the PR. I installed the package and try with AWS Bedrock, does it miss some filed, any idea?

[lidiams96]

@shenxianpeng Thanks for reporting this. I’ve pushed a fix in a new commit—please try again when you can.

Root cause: the Bedrock provider was setting responseFormat in BedrockChatRequestParameters, which isn’t supported by the Bedrock SDK and caused assistant creation to fail. I removed that parameter and added a small test to cover the configuration. All tests pass on my side.

[shenxianpeng]

Thanks @lidiams96! I don’t have an environment available to test it myself, but based on your testing and the screenshot, it looks good. I’m going to go ahead and merge it