[JIRA] (JENKINS-62003) Add build trigger creation to Multibranch Pipeline projects
Title: Message Title Martin Henschke created an issue Jenkins / JENKINS-62003 Add build trigger creation to Multibranch Pipeline projects Issue Type: Improvement Assignee: Atlassian Bitbucket Server Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-22 03:38 Labels: tracked-by-atlassian Priority: Major Reporter: Martin Henschke There is currently no way to register a build trigger in Bitbucket using a multibranch pipeline project. A UI trigger should be added to the configuration page in the same manner as Freestyle and Pipeline projects. Workaround: Until this feature is added, you can still create a webhook in your Bitbucket Server instance manually: Go to your Bitbucket instance, and navigate to the affected repository Go to Settings -> Webhooks -> create Fill in the name and base URL for your Jenkins instance Check the Repository "Push" event
[JIRA] (JENKINS-61786) Add example Jenkinsfile
Title: Message Title Martin Henschke commented on JENKINS-61786 Re: Add example Jenkinsfile Hi Dolan, thanks for your suggestion. Documentation for how to add steps to your Jenkinsfile falls under general Jenkins documentation, which we don't want to replicate in our readme. Resources like this one https://jenkins.io/doc/book/pipeline/syntax/ should explain how to add steps to your declarative pipeline- the `bbs_checkout` step behaves the same as any other generated step. That said, we do intend on adding a pipeline sample file that includes some pre-filled information on your instance that you can use as a template in the future. I will mark this as CWD for now. Thanks, Martin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205625.1585842058000.8521.1586395620487%40Atlassian.JIRA.
[JIRA] (JENKINS-61786) Add example Jenkinsfile
Title: Message Title Martin Henschke closed an issue as Won't Do Jenkins / JENKINS-61786 Add example Jenkinsfile Change By: Martin Henschke Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205625.1585842058000.8518.1586395620445%40Atlassian.JIRA.
[JIRA] (JENKINS-61704) jenkins pipeline job no permission to config bitbucket-server-integration plugin
Title: Message Title Martin Henschke commented on JENKINS-61704 Re: jenkins pipeline job no permission to config bitbucket-server-integration plugin Hi Roy, thanks for this report. Can you please share what plugin you are using for managing permissions, and what authorization strategy you have selected in your global security settings? Thanks, Martin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205529.1585279505000.7959.1586322540122%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke updated JENKINS-60274 Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Status: In Review Closed Resolution: Fixed Released As: 1.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.7934.1586317980846%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke updated JENKINS-60274 Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.7936.1586317980879%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke updated JENKINS-60274 Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.7290.1586231700544%40Atlassian.JIRA.
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke closed an issue as Not A Defect Jenkins / JENKINS-61315 Add documentation for declarative pipeline support. Change By: Martin Henschke Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204901.1583274613000.3397.1585613280351%40Atlassian.JIRA.
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke edited a comment on 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 free to follow up if you have any further questions. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204901.1583274613000.3399.1585613280407%40Atlassian.JIRA.
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Martin Henschke commented on 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. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204901.1583274613000.3393.1585613160224%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke closed an issue as Won't Do Jenkins / JENKINS-61677 Mark PR as Needs Work when build fails Change By: Martin Henschke Status: Open Closed Assignee: Kristy Hughes Martin Henschke Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205414.1585126338000.723.1585259460411%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke edited a comment on JENKINS-61677 Re: Mark PR as Needs Work when build fails Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.You can however make your build statuses more actionable from within Bitbucket by setting up a [ merge check | for minimum successful builds which will restrict merges to PRs with a successful build against them. [https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] ] for minimum successful builds which will restrict merges to PRs with a successful build against them. I will mark this as CWD for now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205414.1585126338000.144.1585185060171%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke commented on JENKINS-61677 Re: Mark PR as Needs Work when build fails Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer. You can however make your build statuses more actionable from within Bitbucket by setting up a [merge check for minimum successful builds|https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html,] which will restrict merges to PRs with a successful build against them. I will mark this as CWD for now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205414.1585126338000.135.1585185000431%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke edited a comment on JENKINS-61677 Re: Mark PR as Needs Work when build fails Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.You can however make your build statuses more actionable from within Bitbucket by setting up a [merge check for minimum successful builds |[https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html]] for minimum successful builds which will restrict merges to PRs with a successful build against them.I will mark this as CWD for now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205414.1585126338000.141.1585185000524%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Martin Henschke edited a comment on JENKINS-61677 Re: Mark PR as Needs Work when build fails Hi Ilya, thanks for your suggestion. Unfortunately, we are not able to mark PRs are Needs Work from Jenkins, as this is an action that needs to be taken by a reviewer.You can however make your build statuses more actionable from within Bitbucket by setting up a [merge check for minimum successful builds|[https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html] , ] which will restrict merges to PRs with a successful build against them.I will mark this as CWD for now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205414.1585126338000.138.1585185000473%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke updated JENKINS-60492 Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.118.1585181700554%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not displaying for multiple jobs
Title: Message Title Martin Henschke updated JENKINS-60956 Jenkins / JENKINS-60956 Build statuses not displaying for multiple jobs Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204416.158077623.1158.1582865282220%40Atlassian.JIRA.
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Martin Henschke updated JENKINS-59804 Jenkins / JENKINS-59804 Support Multibranch Pipelines Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202534.1571228736000.1157.1582865282207%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke updated JENKINS-60809 Jenkins / JENKINS-60809 No GIT_* environment entries set during pipeline run Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1. 0 1 . 5 0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.1160.1582865282243%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke updated JENKINS-60917 Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.1162.1582865282286%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke updated JENKINS-60649 Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.1.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.1144.1582865281959%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke updated JENKINS-60917 Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.1060.1582847580588%40Atlassian.JIRA.
[JIRA] (JENKINS-61180) Cannot delete job after using webhook to bitbucket
Title: Message Title Martin Henschke commented on JENKINS-61180 Re: Cannot delete job after using webhook to bitbucket Hi Sean, The issue seems to be that the webhook log at `C:\Jenkins\jobs\FW-TestJob-01\bitbucket-webhook-trigger.log` is read-only. Changing the permissions (or deleting this file manually) should resolve the issue in this instance. I wasn't able to replicate this issue locally. Are you able to provide steps to reproduce, and some more information about your environment (operating system, other plugins etc.)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204723.1582295097000.5076.1582506300218%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke updated JENKINS-60917 Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.5067.1582504320881%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke started work on JENKINS-60917 Change By: Martin Henschke Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.5065.1582504320830%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke started work on JENKINS-60492 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.4062.1582251420635%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Martin Henschke Assignee: Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.4060.1582251420607%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke updated JENKINS-60649 Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.6341.1581404280529%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke updated JENKINS-60649 Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.6336.1581404221452%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke edited a comment on JENKINS-60492 Re: Connection with Bitbucket server over SSH Hi Roman,This was intended for the first release of the plugin- only login-password credentials are provided so I will change the type of this ticket to " improvement new feature ". Thanks for the suggestion- we will consider it for a future release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6143.1581381720589%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke updated an issue Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Martin Henschke Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6134.1581381661019%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke commented on JENKINS-60492 Re: Connection with Bitbucket server over SSH Hi Roman, This was intended for the first release of the plugin- only login-password credentials are provided so I will change the type of this ticket to "improvement". Thanks for the suggestion- we will consider it for a future release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.6129.1581381660926%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke started work on JENKINS-60274 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.1450.1580850243073%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Martin Henschke Assignee: Trung Nguyen Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.1437.1580850242803%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.1448.1580850243052%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke started work on JENKINS-60649 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.1439.1580850242911%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke updated JENKINS-60809 Jenkins / JENKINS-60809 No GIT_* environment entries set during pipeline run Change By: Martin Henschke Status: In Progress Fixed but Unreleased Resolution: Fixed Released As: 1.0.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.1432.1580850242544%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not displaying for multiple jobs
Title: Message Title Martin Henschke updated an issue Jenkins / JENKINS-60956 Build statuses not displaying for multiple jobs Change By: Martin Henschke Summary: Build statuses not working displaying for multiple jobs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204416.158077623.659.1580777640071%40Atlassian.JIRA.
[JIRA] (JENKINS-60956) Build statuses not working for multiple jobs
Title: Message Title Martin Henschke created an issue Jenkins / JENKINS-60956 Build statuses not working for multiple jobs Issue Type: Bug Assignee: Martin Henschke Components: atlassian-bitbucket-server-integration-plugin Created: 2020-02-04 00:30 Environment: Jenkins 2.164 Priority: Major Reporter: Martin Henschke Build statuses are currently identified simply as an integer, with no differentiation between jobs. This leads to only one job's build status actually being visible in Bitbucket Server. Steps to replicate: Create two projects for two separate repositories in Bitbucket Server Run a build for each project once Expected result: Both commits have a build status visible in Bitbucket Server Actual result: Only one commit has a build status Add Comment
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Martin Henschke commented on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
Hi Bruce, I wasn't able to reproduce this issue. I created an environment table similar to [this|https://jenkins.io/doc/pipeline/tour/environment/,] and the variable was substituted correctly. I notice in your example, you use single quotes- which when I did would attempt to scan for a branch named literally named ${ENV_VARNAME}, but with double quotes, the name was correctly substituted. Could you possibly provide a more complete Jenkinsfile and a snippet from the build logs, so we can investigate further?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203446.157565559.604.1580774100302%40Atlassian.JIRA.
[JIRA] (JENKINS-60392) Allow environment variables with Bitbucket Server Integration Pipeline
Title: Message Title
Martin Henschke edited a comment on JENKINS-60392
Re: Allow environment variables with Bitbucket Server Integration Pipeline
Hi Bruce,I wasn't able to reproduce this issue. I created an environment table similar to [ this|[ https://jenkins.io/doc/pipeline/tour/environment/] ,] and the variable was substituted correctly. I notice in your example, you use single quotes- which when I did would attempt to scan for a branch named literally named ${ENV_VARNAME}, but with double quotes, the name was correctly substituted.Could you possibly provide a more complete Jenkinsfile and a snippet from the build logs, so we can investigate further?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203446.157565559.608.1580774100386%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke started work on JENKINS-60809 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.601.1580770320636%40Atlassian.JIRA.
[JIRA] (JENKINS-60809) No GIT_* environment entries set during pipeline run
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60809 No GIT_* environment entries set during pipeline run Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204140.1579280474000.599.1580770320542%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke commented on JENKINS-60917 Re: Jenkins Pipeline requires at least one successfull build for the trigger to work Hi Sven, My initial read of the bug suggested this was likely the same root cause as JENKINS-60649- but doing a bit more investigation it looks like they have separate causes. Accordingly, I've reopened the ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.10538.1580678880151%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke reopened an issue Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Resolution: Duplicate Status: Closed Reopened Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.10536.1580678820352%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke closed an issue as Duplicate Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.9075.1580421180375%40Atlassian.JIRA.
[JIRA] (JENKINS-60490) Job/Configure permission required to configure jobs
Title: Message Title Martin Henschke started work on JENKINS-60490 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203579.1576451961000.7013.1580166000665%40Atlassian.JIRA.
[JIRA] (JENKINS-60490) Job/Configure permission required to configure jobs
Title: Message Title Martin Henschke closed an issue as Duplicate Jenkins / JENKINS-60490 Job/Configure permission required to configure jobs Change By: Martin Henschke Status: In Progress Closed Assignee: Kristy Hughes Martin Henschke Resolution: Duplicate Released As: 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke updated JENKINS-60642 Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.7008.1580165940531%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke updated JENKINS-60699 Jenkins / JENKINS-60699 Cannot add bitbucket server Change By: Martin Henschke Status: Fixed but Unreleased Closed Released As: 1.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.7001.1580165880582%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke edited a comment on JENKINS-60699 Re: Cannot add bitbucket server A quick update on this issue:This bug was related to https://issues.jenkins-ci.org/browse/JENKINS-60816 , which has been resolved in Jenkins version 2.217, so upgrading your instance to that version should resolve the issue.We have also created a fix for this issue, still affecting versions 2.212-2.215, that will appear in 1. 05 04 of the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.6994.1580165700299%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke commented on JENKINS-60699 Re: Cannot add bitbucket server A quick update on this issue: This bug was related to https://issues.jenkins-ci.org/browse/JENKINS-60816 , which has been resolved in Jenkins version 2.217, so upgrading your instance to that version should resolve the issue. We have also created a fix for this issue, still affecting versions 2.212-2.215, that will appear in 1.05 of the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.4702.1579819740254%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke updated JENKINS-60699 Jenkins / JENKINS-60699 Cannot add bitbucket server Change By: Martin Henschke Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.4617.1579816200609%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke updated JENKINS-60642 Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Change By: Martin Henschke Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.3513.1579645140395%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke updated JENKINS-60699 Jenkins / JENKINS-60699 Cannot add bitbucket server Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.3506.1579645020592%40Atlassian.JIRA.
[JIRA] (JENKINS-60816) ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface
Title: Message Title
Martin Henschke updated an issue
Jenkins / JENKINS-60816
ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface
Change By:
Martin Henschke
When loading the Bitbucket Server Integration plugin from a clean install of Jenkins version 2.213 and above, several entries in the stack trace are appearing. I'm looking to find a fix for the problem for the plugin, but it appears the root of the issue is in Jenkins Extension Finder:{code:java}hudson.ExtensionFinder$GuiceFinder$SezpozModule configure WARNING: Failed to load com.atlassian.bitbucket.jenkins.internal.config.BitbucketServerConfiguration$DescriptorImpl java.lang.LinkageError: Failed to resolve interface com.atlassian.bitbucket.jenkins.internal.credentials.JenkinsToBitbucketCredentials at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:516) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:510) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:487) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:536) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) at com.google.inject.spi.Elements.getElements(Elements.java:110) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:285) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:714) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:700) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1172) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:102) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:177) at
[JIRA] (JENKINS-60816) ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface
Title: Message Title
Martin Henschke updated an issue
Jenkins / JENKINS-60816
ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface
Change By:
Martin Henschke
When loading the Bitbucket Server Integration plugin from a clean install of Jenkins version 2.213 and above, several entries in the stack trace are appearing. I'm looking to find a fix for the problem for the plugin, but it appears the root of the issue is in Jenkins Extension Finder: {code:java} ``` hudson.ExtensionFinder$GuiceFinder$SezpozModule configureWARNING: Failed to load com.atlassian.bitbucket.jenkins.internal.config.BitbucketServerConfiguration$DescriptorImpljava.lang.LinkageError: Failed to resolve interface com.atlassian.bitbucket.jenkins.internal.credentials.JenkinsToBitbucketCredentials at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:516) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:510) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:487) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:536) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340) at com.google.inject.spi.Elements.getElements(Elements.java:110) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:285) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:714) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:700) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1172) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:109) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:102) at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:177) at
[JIRA] (JENKINS-60816) ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface
Title: Message Title Martin Henschke created an issue Jenkins / JENKINS-60816 ExtensionFinder Failed to resolve interface when resolving descriptor with injected interface Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-20 05:23 Environment: Jenkins version 2.213 Mac OS 10.14.6 Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) Plugins: Bitbucket Server Integration (atlassian-bitbucket-server-integration): 1.0.4 JSch dependency plugin (jsch): 0.1.54.1 Structs Plugin (structs): 1.19 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 Pipeline: Declarative Extension Points API (pipeline-model-extensions): 1.3.2 Pipeline (workflow-aggregator): 2.6 Mailer Plugin (mailer): 1.21 Git plugin (git): 3.12.1 Command Agent Launcher Plugin (command-launcher): 1.2 Pipeline: API (workflow-api): 2.29 Pipeline: Job (workflow-job): 2.25 SSH Credentials Plugin (ssh-credentials): 1.13 Authentication Tokens API Plugin (authentication-tokens): 1.1 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.11 Jackson 2 API Plugin (jackson2-api): 2.8.11.3 Docker Pipeline (docker-workflow): 1.14 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 Credentials Plugin (credentials): 2.3.0 Lockable Resources plugin (lockable-resources): 2.3 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 Pipeline: SCM Step (workflow-scm-step): 2.7 Matrix Authorization Strategy Plugin (matrix-auth): 2.3 Matrix Project Plugin (matrix-project): 1.14 Pipeline: Stage Step (pipeline-stage-step): 2.3 Pipeline: Build Step (pipeline-build-step): 2.7 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.1 Pipeline: Input Step (pipeline-input-step): 2.8 bouncycastle API Plugin (bouncycastle-api): 2.16.0 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1 Plain Credentials Plugin (plain-credentials): 1.5 Docker Commons Plugin (docker-commons): 1.5 Git client plugin (git-client): 2.7.7 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Basic Steps (workflow-basic-steps): 2.11 Credentials Binding Plugin (credentials-binding): 1.13 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 Pipeline: Multibranch (workflow-multibranch): 2.20 Script Security Plugin (script-security): 1.68 GIT server Plugin (git-server): 1.7
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60699 Cannot add bitbucket server Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.2297.1579473121100%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke updated JENKINS-60642 Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Change By: Martin Henschke Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.2290.1579473120926%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke started work on JENKINS-60699 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.2299.1579473121123%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Change By: Martin Henschke Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.818.1579226100254%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke closed an issue as Duplicate Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.814.1579225980768%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke updated JENKINS-60475 Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.810.1579225980699%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Martin Henschke updated JENKINS-60475 Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Change By: Martin Henschke Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203557.1576239833000.806.1579225920444%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Martin Henschke commented on JENKINS-60699 Re: Cannot add bitbucket server Hi Davis, Thanks for reporting this issue. We're aware of it, and it appears to be linked to the version of Jenkins (2.213), but it needs further investigation. As of right now, we're not aware of a workaround for this issue. We're looking into a fix and will keep this issue updated on our progress. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203944.1578501772000.764.1579220400269%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Martin Henschke started work on JENKINS-60642 Change By: Martin Henschke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.742.1579218540829%40Atlassian.JIRA.
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Martin Henschke commented on JENKINS-60649 Re: Bitbucket Server Integration plugin does not work for Pipelines Hi Trung, thanks for reporting this. We are aware of the issue and are looking at solutions. In the meantime, there is a workaround to this issue: Create your pipelines project as normal. Within that project, start a build of that project and wait for it to resolve (it does not need to be successful, just running it is enough) Once completed, click "configure" to go back to the project configuration Ensure the "Bitbucket Server trigger build after push" build trigger is checked Save the project configuration This should trigger the webhook to be created in Bitbucket Server. If you're having trouble with this solution, you can also create a webhook manually in your repository settings- create it with the URL `http:///bitbucket-server-webhook/trigger`, with the secret field empty, and with the "push" event checked. Feel free to reach out if you have any other issues. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
