• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: atlassian-bitbucket-server-integration-plugin
• Labels:

  • tracked-by-atlassian
• Environment:

  jenkins:2.190.1
  atlassian-bitbucket-server-integration:1.0.3
  bitbucket-server:5.12

1. 

   after_save.png

   106 kB

   2019-11-25 20:49

2. 

   build_status.png

   67 kB

   2019-11-25 20:49

3. 

   config_work.png

   125 kB

   2019-11-25 20:49

[JENKINS-60274] Unable to use plugin with private Bitbucket repositories

Valentin Delaye created issue - 2019-11-25 20:50

Valentin Delaye made changes - 2019-11-25 20:50

Description

Original: Hi! We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~). It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work. To reproduce - Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated - Save the pipeline The pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.png We don't have this problem with standard Bitbucket project

New: Hi! We are trying to use this plugin, but we have issue to configure it with private repositories (starting with ~). It seems at some point the plugin "replace" the ~username by the full display name. Which obviously doesn't work. To reproduce - Configure a standard pipeline with a private repo (screenshot config_work.png). Configuration is validated - Save the pipeline The pipeline cannot build and when we want to configure it again it seems that the "Display" name of the user was replaced on the configuration (build_status.png) and after_save.png We don't have this problem with standard Bitbucket project. Thanks. Valentin

Collapse comment: John Lawlor added a comment - 2019-11-27 11:11, Edited by John Lawlor - 2019-11-27 11:16

John Lawlor added a comment - 2019-11-27 11:11 - edited

I am also seeing this problem on Bitbucket 6.8.0, Jenkins 2.190.2 and the latest version of the plugin 1.0.3.

Expand comment: John Lawlor added a comment - 2019-11-27 11:11, Edited by John Lawlor - 2019-11-27 11:16

John Lawlor added a comment - 2019-11-27 11:11 - edited I am also seeing this problem on Bitbucket 6.8.0, Jenkins 2.190.2 and the latest version of the plugin 1.0.3.

Martin Henschke made changes - 2020-02-04 21:03

Assignee

Original: Kristy Hughes [ khughes ]

New: Martin Henschke [ mhenschke_atlassian ]

Martin Henschke made changes - 2020-02-04 21:03

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

B Plump made changes - 2020-03-30 02:57

Labels

New: tracked-by-atlassian

Martin Henschke made changes - 2020-04-07 03:54

Status

Original: In Progress [ 3 ]

New: In Review [ 10005 ]

Martin Henschke made changes - 2020-04-08 03:52

Released As		New: 1.1.1
Resolution		New: Fixed [ 1 ]
Status	Original: In Review [ 10005 ]	New: Closed [ 6 ]

Martin Henschke made changes - 2020-04-08 03:52

Status

Original: Closed [ 6 ]

New: Fixed but Unreleased [ 10203 ]

Martin Henschke made changes - 2020-07-07 02:35

Link

New: This issue is duplicated by JENKINS-62786 [ JENKINS-62786 ]

Load more newer events