Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47111

ERROR: [GitHub Commit Status Setter] - {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","field":"description","message":"description is too long (maximum is 140 characters)"}],"

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • github-plugin
    • None

      I am constantly getting this error message when trying to post a status update back to my Github Enterprise server

      Github Plugin: 1.28.0
      Github Enterprise: 2.10

      [PostBuildScript] - Execution post build scripts.
      [chef-environments] $ /bin/sh -xe /tmp/hudson5503619536866319144.sh
      [PostBuildScript] - Execution post build scripts.
      [chef-environments] $ /bin/sh -xe /tmp/hudson5503619536866319144.sh
      [Set GitHub commit status (universal)] SUCCESS on repos [GHRepository@4198b907[description=Roles, Environments, Databags, etc. ,homepage=,name=chef-environments,license=<null>,fork=false,size=3040,milestones={},language=Ruby,commits={},source=<null>,parent=<null>,responseHeaderFields={null=[HTTP/1.1 200 OK], Access-Control-Allow-Origin=[*], Access-Control-Expose-Headers=[ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval], Cache-Control=[private, max-age=60, s-maxage=60], Content-Length=[7467], Content-Security-Policy=[default-src 'none'], Content-Type=[application/json; charset=utf-8], Date=[Mon, 25 Sep 2017 20:40:11 GMT], ETag=["1c83ea56c28a2ef1f13351b1be02361f"], Last-Modified=[Fri, 26 May 2017 15:52:00 GMT], OkHttp-Received-Millis=[1506372010714], OkHttp-Response-Source=[CONDITIONAL_CACHE 304], OkHttp-Selected-Protocol=[http/1.1], OkHttp-Sent-Millis=[1506372010544], Server=[GitHub.com], Status=[304 Not Modified], Strict-Transport-Security=[max-age=31536000; includeSubdomains], Vary=[Accept, Authorization, Cookie, X-GitHub-OTP], X-Accepted-OAuth-Scopes=[repo], X-Content-Type-Options=[nosniff], X-Frame-Options=[deny], X-GitHub-Media-Type=[github.v3; format=json], X-GitHub-Request-Id=[f7b07d38-53ad-4640-b423-77c2fd7f8a24], X-OAuth-Scopes=[admin:repo_hook, repo], X-XSS-Protection=[1; mode=block]},url=https://sqbu-github.xxxxxx.com/api/v3/repos/tropo-operations/chef-environments,id=5918]] (sha:99e77f0) with context:chef-environments
      Setting commit status on GitHub for https://sqbu-github.xxxxxx.com/tropo-operations/chef-environments/commit/99e77f06d9953e0c03079396c2a8c0db3a8ee93e
      ERROR: [GitHub Commit Status Setter] - {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","field":"description","message":"description is too long (maximum is 140 characters)"}],"documentation_url":"https://developer.github.com/enterprise/2.10/v3/repos/statuses/#create-a-status"}, setting build result to FAILURE
      Build step 'Set build status on GitHub commit [deprecated]' changed build result to FAILURESetting commit status on GitHub for https://sqbu-github.cisco.com/tropo-operations/chef-environments/commit/99e77f06d9953e0c03079396c2a8c0db3a8ee93e
      ERROR: [GitHub Commit Status Setter] - {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","field":"description","message":"description is too long (maximum is 140 characters)"}],"documentation_url":"https://developer.github.com/enterprise/2.10/v3/repos/statuses/#create-a-status"}, setting build result to FAILURE
      Build step 'Set build status on GitHub commit [deprecated]' changed build result to FAILURE

      I understand the the description of a PR apparently cant exceed 140 characters but I dont see how I am exceeding that in my PR... Please advise

          [JENKINS-47111] ERROR: [GitHub Commit Status Setter] - {"message":"Validation Failed","errors":[{"resource":"Status","code":"custom","field":"description","message":"description is too long (maximum is 140 characters)"}],"

          Probably too long job name?

           

          Why you using both types of status setter? (universal and deprecated?)

          Kirill Merkushev added a comment - Probably too long job name?   Why you using both types of status setter? (universal and deprecated?)

          John Dyer added a comment -

          lanwen - So I was testing both trying to get a handle on the issue, I guess the log above still had them both enabled. I still dont see the job name exceeding 140 characters?

          Build #924 origin/change/OPS-8294_Add_jdbc_timeouts_to_gw,_runtimes,_and_papi_Softlayer_wdc_legacy_roles_runtime_wdc_huron_dev.rb
          

          by my count thats 129 characters

          John Dyer added a comment - lanwen - So I was testing both trying to get a handle on the issue, I guess the log above still had them both enabled. I still dont see the job name exceeding 140 characters? Build #924 origin/change/OPS-8294_Add_jdbc_timeouts_to_gw,_runtimes,_and_papi_Softlayer_wdc_legacy_roles_runtime_wdc_huron_dev.rb by my count thats 129 characters

            lanwen Kirill Merkushev
            johntdyer John Dyer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: