add job name in log file when logging an error.

[moshavnik]

Problem

What problem does this solve?
currently, the log file contains an entry for each failed request to the ai source. the log posts the response from the ai to help analyzing the problem.
however, in our case, there is a single error during a period with a lot of running jobs (all of them using the ai at the same time) and there is no indication in the log which job suffered the error.
in addition - the explainError method doesn't fail, so we don't know which job failed to use the ai mechanism and need to sort through a lot of jobs in order to find it.

Solution

Describe your proposed solution:
add the job complete name to the log, and the build number - right next to the error message.

Alternatives

What alternative approaches have you considered?
make the explainError method return a value which can be analyzes whether the ai mechanism returned a response or not.

Additional Context

Screenshots, examples, or other relevant information:

[shenxianpeng]

@moshavnik Thanks for reporting the issue.

I have PR #22. Could you please review the screenshots in #22 (comment) and let me know if it works as you expected?

[moshavnik]

hi @shenxianpeng ,
I think I didn't explain myself the proper way.
what I meant was - I need information about the job in the jenkins controller log file (on the server itself, not the job...).
when there is a problem accessing the ai engine, all I get in the jenkins controller file is the response and error code, but there is no indication in the error - which job was executed, so i cannot further investigate the problem.

what you are showing here is a good addition to the job itself (from the end user point of view), and what i requested was better logging for the jenkins controller administrator (more information in the jenkins.log file)... :)

[shenxianpeng]

Hi @moshavnik

I have added job info to the system log now. Can you please take a look at the new changes #25 (comment) to see if it works as you expect

[moshavnik]

hi @shenxianpeng ,

thanks! that's exactly what we needed :)

waiting for the next official plugin release to be available...