[JIRA] (JENKINS-36874) Pull request not built when build status patch is applied

30 views
Skip to first unread message

pavlyshko-m@yandex.by (JIRA)

unread,
Jul 22, 2016, 7:57:02 AM7/22/16
to jenkinsc...@googlegroups.com
Mikhail Paulyshka created an issue
 
Jenkins / Bug JENKINS-36874
Pull request not built when build status patch is applied
Issue Type: Bug Bug
Assignee: Antonio Muñiz
Components: bitbucket-branch-source-plugin
Created: 2016/Jul/22 11:56 AM
Environment: Jenkins 2.14
bitbucket-branch-source-plugin from github master branch
Priority: Minor Minor
Reporter: Mikhail Paulyshka

When user send pull request

[Bitbucket] Notifying commit build result
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 400: BAD REQUEST.
{"error": {"fields": {"key": ["Ensure this value has at most 40 characters (it has 54)."]}, "message": "Bad request"}}
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:486)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:513)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postBuildStatus(BitbucketCloudApiClient.java:303)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketChangesetCommentNotifier.buildStatus(BitbucketChangesetCommentNotifier.java:49)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.createBuildCommitStatus(BitbucketBuildStatusNotifications.java:85)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.sendNotifications(BitbucketBuildStatusNotifications.java:171)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.access$000(BitbucketBuildStatusNotifications.java:60)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications$JobCheckOutListener.onCheckout(BitbucketBuildStatusNotifications.java:190)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123)
	at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
	at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:404)
Finished: FAILURE

PR link: https://bitbucket.org/XVM/xvm/pull-requests/288/battlelabels-descripton-typo/

Full Log: http://ci.modxvm.com/job/XVM/job/demon2597%252Fbattlelabels-descripton-typo-1469180738999/1/console
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

pavlyshko-m@yandex.by (JIRA)

unread,
Jul 22, 2016, 7:59:01 AM7/22/16
to jenkinsc...@googlegroups.com
Mikhail Paulyshka updated an issue
Change By: Mikhail Paulyshka
When user send pull request


{code:java}

[Bitbucket] Notifying commit build result
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 400: BAD REQUEST.
{"error": {"fields": {"key": ["Ensure this value has at most 40 characters (it has 54)."]}, "message": "Bad request"}}
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:486)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:513)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postBuildStatus(BitbucketCloudApiClient.java:303)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketChangesetCommentNotifier.buildStatus(BitbucketChangesetCommentNotifier.java:49)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.createBuildCommitStatus(BitbucketBuildStatusNotifications.java:85)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.sendNotifications(BitbucketBuildStatusNotifications.java:171)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.access$000(BitbucketBuildStatusNotifications.java:60)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications$JobCheckOutListener.onCheckout(BitbucketBuildStatusNotifications.java:190)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Finished: FAILURE

amuniz@cloudbees.com (JIRA)

unread,
Jul 25, 2016, 3:44:01 AM7/25/16
to jenkinsc...@googlegroups.com
Antonio Muñiz commented on Bug JENKINS-36874
 
Re: Pull request not built when build status patch is applied

Did you have the Jenkins root URL set to something that is not localhost?

pavlyshko-m@yandex.by (JIRA)

unread,
Jul 25, 2016, 12:16:01 PM7/25/16
to jenkinsc...@googlegroups.com

Jenkins root URL set to "https://ci.modxvm.com".

The problem occurs only with a pull requests. Commits in the repository branches going fine.

amuniz@cloudbees.com (JIRA)

unread,
Jul 26, 2016, 5:33:01 AM7/26/16
to jenkinsc...@googlegroups.com

Ok, I see Ensure this value has at most 40 characters (it has 54).. The message needs to be shortened a bit, I didn't hit this before.

amuniz@cloudbees.com (JIRA)

unread,
Jul 26, 2016, 5:33:02 AM7/26/16
to jenkinsc...@googlegroups.com
Antonio Muñiz edited a comment on Bug JENKINS-36874
Ok, I see {{Ensure this value has at most 40 characters (it has 54).}} . The message needs to be shortened a bit, I didn't hit this before.

pavlyshko-m@yandex.by (JIRA)

unread,
Jul 26, 2016, 7:55:02 AM7/26/16
to jenkinsc...@googlegroups.com

amuniz@cloudbees.com (JIRA)

unread,
Dec 28, 2016, 7:21:01 AM12/28/16
to jenkinsc...@googlegroups.com
Antonio Muñiz resolved as Fixed
 
Change By: Antonio Muñiz
Status: Open Resolved
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages