Search before asking
What happened
A user triggered the error as follows:
subtask extractApiBuilds ended unexpectedly caused by: error adding the result to batch caused by: Error 1406: Data too long for column 'full_display_name' at row 138
As we see in the code, full_display_name has come from Jenkins API. and it limits by 255 in the tool layer.
in the domain layer. it will convert to the CICD name and limit by 255.
Since fullname and jobpath have a high probability of being too long when FullDisplayName is too long, the above fields may also have the same problem and need to be dealt with.
What do you expect to happen
Jenkins can get data success.
How to reproduce
With a very deep and long path to save Jenkins jobs.
Anything else
No response
Version
main
Are you willing to submit PR?
Code of Conduct
Search before asking
What happened
A user triggered the error as follows:
subtask extractApiBuilds ended unexpectedly caused by: error adding the result to batch caused by: Error 1406: Data too long for column 'full_display_name' at row 138As we see in the code, full_display_name has come from Jenkins API. and it limits by 255 in the tool layer.
in the domain layer. it will convert to the CICD name and limit by 255.
Since
fullnameandjobpathhave a high probability of being too long when FullDisplayName is too long, the above fields may also have the same problem and need to be dealt with.What do you expect to happen
Jenkins can get data success.
How to reproduce
With a very deep and long path to save Jenkins jobs.
Anything else
No response
Version
main
Are you willing to submit PR?
Code of Conduct