• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: jira-plugin
• Labels:

  • atlassian
  • comment
  • jira
  • limit
• Environment:

  Jenkins:2.229
  Jira plugin (jira): 3.1.3
  

[JENKINS-65496] Huge JIRA comments generated by "Update relevant issues" are silently rejected.

Victor Dulepov created issue - 2021-04-28 07:17

Victor Dulepov made changes - 2021-04-28 07:22

Issue Type

Original: Improvement [ 4 ]

New: Bug [ 1 ]

Victor Dulepov made changes - 2021-04-28 09:02

Description

Original: A big merge or a change involving lots of files easily produces a huge comment, especially when "Record Scm changes" is turned on.  Jira typically has a limit on the comment size, and when Jenkins attempts to put in such a huge comment, the updater fails as below: {code} 2021-04-23 10:43:26.704+0000 [id=21943] WARNING h.plugins.jira.JiraRestService#addComment: Jira REST client add comment error. cause: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={comment=The entered text is too long. It exceeds the allowed limit of 32767 characters.}, errorMessages=[]}]} RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={comment=The entered text is too long. It exceeds the allowed limit of 32767 characters.}, errorMessages=[]}]} at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:176) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:170) {code} These JIRA update failures are not reflected in the job console log (it only puts out several {{[Jira] Updating issue KEY-1234}} ), so there's no way to tell what went wrong unless you look up the actual Jenkins log. EXPECTED: 1. report JIRA update failures in the job console log 2. add a parameter ("max. comment length" or whatever) in the global configuration for the Jira plugin. Truncate generated comments according to this limit (possibly, attempting to close any fancy formatting tags at the end, but that's not critical).

New: A big merge or a change involving lots of files easily produces a huge comment, especially when "Record Scm changes" is turned on.  Jira typically has a limit on the comment size, and when Jenkins attempts to put in such a huge comment, the updater fails as below: {code} 2021-04-23 10:43:26.704+0000 [id=21943] WARNING h.plugins.jira.JiraRestService#addComment: Jira REST client add comment error. cause: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={comment=The entered text is too long. It exceeds the allowed limit of 32767 characters.}, errorMessages=[]}]} RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={comment=The entered text is too long. It exceeds the allowed limit of 32767 characters.}, errorMessages=[]}]} at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:176) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:170) {code} These JIRA update failures are not reflected in the job console log (it only puts out several {{[Jira] Updating issue KEY-1234}} ), so there's no way to tell what went wrong unless you look up the actual Jenkins log. EXPECTED: 1. report JIRA update failures in the job console log 2. add a parameter ("max. comment length" or whatever) in the global configuration for the Jira plugin. Truncate generated comments according to this limit (possibly, attempting to close any fancy formatting tags at the end, but that's not critical). It's also quite possible that one may need to see the SCM details fetched by "record SCM changes" in Jenkins' web UI, but omit them in the JIRA comments. I do not see how to achieve this having only a single checkbox in the Configuration.

Mark Waite made changes - 2023-07-24 13:14

Comment

[ You should see connection headers when you run curl -v, but I don't see them here. Additionally, you can use the word "code" to structure your code, or you can just attach a text file.  [free games|https://freegamesonline.io] ]

Mark Waite made changes - 2023-07-24 13:15

Comment

[ You should see connection headers when you run curl -v, but I don't see them here. [https://www.jenkins.io/doc/book/managing/system-properties/#hudson-model-workspacecleanupthread-retainfordays] [free games|https://freegamesonline.io] Additionally, you can use the word "code" to structure your code, or you can just attach a text file.  ]

Damien Duportal made changes - 2023-08-14 16:18

Comment

[ [Geometry Dash Scratch|https://geometrydashscratch.io/]  is a fan-made adaptation of the popular rhythm-based platform game, Geometry Dash, created using the Scratch programming language. In this version, players can create their own levels, share them with the community, and play levels made by other users. ]

Damien Duportal made changes - 2023-08-14 16:18

Comment

[ Thank you so much for sharing this interesting idea. The views in the article are extremely insightful and factual. I like it very much. Hope you will continue to have more articles like this. ]

Damien Duportal made changes - 2023-08-14 16:18

Comment

[ Has this issue been resolved?  ]

Damien Duportal made changes - 2023-08-14 16:18

Comment

[  [ You should see connection headers when you run curl -v, but I don't see them here. Additionally, you can use the word "code" to structure your code, or you can just attach a text file.  [ You should see connection headers when you run curl -v, but I don't see them here. Additionally, you can use the word "code" to structure your code, or you can just attach a text file. ** ]