Get the log of the error, then suggest solution to user.

In normal businesses, identity management and access management are not important, so Jenkins is only used for building/deploying. In financial sector, IAM has to conform to audit standard. This leads to the fragmentation of three areas:

• Identity
• Authentication
• Authorization This makes it hard to onboard application teams to Jenkins. Besides, engineers rarely touch DevOps tools. Quite a few principals do not know how to debug. This system aims to fix this.

• Put a try-catch around the DSL. This will capture the log and send it to the reporting site.
• A pattern matcher on the reporting site will do a regex match and suggest solutions. This can be replaced by an AI/learning algorithm as needed.

sequenceDiagram
participant Stage
participant DSL
participant Aggregation
participant Suggester
participant Reporting

Stage ->> DSL: Call DSL step
opt if fail
	DSL ->> Aggregation: capture the error and build info send to log aggregator
	Suggester ->> Aggregation: fetch the error and do regex match
	Aggregation -->> Suggester: provide log
	Suggester -x Reporting: give failure cause analysis and send log
end
opt if succeed
	DSL ->> Stage: Continue as usual
end