[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.

4 views
Skip to first unread message

timblaktu@gmail.com (JIRA)

unread,
Mar 3, 2020, 5:31:08 PM3/3/20
to jenkinsc...@googlegroups.com
Tim Black created an issue
 
Jenkins / Bug JENKINS-61315
Add documentation for declarative pipeline support.
Issue Type: Bug Bug
Assignee: Kristy Hughes
Components: atlassian-bitbucket-server-integration-plugin
Created: 2020-03-03 22:30
Environment: Bitbucket Server 6.10.1 and Jenkins 2.190.3, with Bitbucket Server Integration plugin 1.1.0.
Priority: Minor Minor
Reporter: Tim Black

I was under the impression (from the release notes) that this plugin offered more configurable runtime functionality through declarative pipelines than is documented. The info pages for this plugin only describe how to connect Jenkins with Bitbucket and to set up a job that uses a Bitbucket repo. It does mention that build status is automatically updated in Bitbucket once the association has been made, but there is no documentation or elaboration of where this is posted or how this status is used.

Is there any support for multibranch pipeline? I would like to implement Merge Checks in Bitbucket PRs which would run the corresponding multibranch pipeline build for the hypothetically-merged branch, and would use the result as a Merge Check, preventing merges when the jenkins build is not Successful. This plugin does not appear to help with this. Am I missing something?

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

dkjellin@atlassian.com (JIRA)

unread,
Mar 15, 2020, 7:54:05 PM3/15/20
to jenkinsc...@googlegroups.com
Daniel Kjellin assigned an issue to Unassigned
Change By: Daniel Kjellin
Assignee: Kristy Hughes

mhenschke@atlassian.com (JIRA)

unread,
Mar 30, 2020, 8:06:03 PM3/30/20
to jenkinsc...@googlegroups.com
Martin Henschke commented on Bug JENKINS-61315
 
Re: Add documentation for declarative pipeline support.

Hi Tim, thanks for the report.

If I understand your report correctly, you want Bitbucket Server to perform a merge on your PR branch without modifying the target branch, and having that build status used as the condition for your merge check. Unfortunately, this is a limitation in Bitbucket Server rather than in Jenkins- the plugin will register a build against the commit on the target branch rather than a merged commit, and that is used for the merge check instead. We do not provide any in-product support for build statuses against a merge build of a PR before it has been merged.

Based on this however, I feel this is not specifically an issue with the Jenkins plugin documentation, so I will close this ticket for now. Please feel to follow up if you have any further questions.

mhenschke@atlassian.com (JIRA)

unread,
Mar 30, 2020, 8:08:02 PM3/30/20
to jenkinsc...@googlegroups.com
Martin Henschke edited a comment on Bug JENKINS-61315
Hi Tim, thanks for the report.

If I understand your report correctly, you want Bitbucket Server to perform a merge on your PR branch without modifying the target branch, and having that build status used as the condition for your merge check. Unfortunately, this is a limitation in Bitbucket Server rather than in Jenkins- the plugin will register a build against the commit on the target branch rather than a merged commit, and that is used for the merge check instead. We do not provide any in-product support for build statuses against a merge build of a PR before it has been merged.

Based on this however, I feel this is not specifically an issue with the Jenkins plugin documentation, so I will close this ticket for now. Please feel free to follow up if you have any further questions.

mhenschke@atlassian.com (JIRA)

unread,
Mar 30, 2020, 8:08:03 PM3/30/20
to jenkinsc...@googlegroups.com
Martin Henschke closed an issue as Not A Defect
 
Change By: Martin Henschke
Status: Open Closed
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages