• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Component/s: atlassian-bitbucket-server-integration-plugin
• Labels:

  • credentials
• Environment:

  Atlassian Bitbucket v.6.7.1
  Jenkins v.2.190.3
  Bitbucket Server Integration v.1.0.3

[JENKINS-60341] Allow configuring the plugin to use Jenkins domain credentials

Javier Rodríguez created issue - 2019-12-02 10:47

Javier Rodríguez made changes - 2019-12-02 11:56

Summary

Original: Allow the configuration of Jenkins domain credentials

New: Allow configuring the plugin to use Jenkins domain credentials

Daniel Kjellin made changes - 2020-02-13 02:48

Assignee

Original: Kristy Hughes [ khughes ]

Miroslav Botta made changes - 2020-09-08 13:04

Link

New: This issue is related to JENKINS-63009 [ JENKINS-63009 ]

Collapse comment: Kalle Niemitalo added a comment - 2021-01-04 10:31

Kalle Niemitalo added a comment - 2021-01-04 10:31

Does this request specifically mean matching the Bitbucket Server REST API URL to the specification of the credential domain? For example, a Jenkins administrator could define a credential domain for hostname "bitbucket1.example.com" and another for hostname "bitbucket2.example.com", and add a Bitbucket personal access token credential in each credential domain; then if the repository is within https://bitbucket2.example.com:7990/, the plugin should get the credential from the corresponding credential domain.

That's what I'd expect it to mean, but the link to JENKINS-63009 makes me unsure.

Expand comment: Kalle Niemitalo added a comment - 2021-01-04 10:31

Kalle Niemitalo added a comment - 2021-01-04 10:31 Does this request specifically mean matching the Bitbucket Server REST API URL to the specification of the credential domain? For example, a Jenkins administrator could define a credential domain for hostname "bitbucket1.example.com" and another for hostname "bitbucket2.example.com", and add a Bitbucket personal access token credential in each credential domain; then if the repository is within https://bitbucket2.example.com:7990/ , the plugin should get the credential from the corresponding credential domain. That's what I'd expect it to mean, but the link to JENKINS-63009 makes me unsure.

Collapse comment: Martin Henschke added a comment - 2021-02-03 05:50, Edited by Martin Henschke - 2021-02-03 05:50

Martin Henschke added a comment - 2021-02-03 05:50 - edited

Hi Javier, thanks for your report.
Can you please add the following things to your request:

• Your usecase
• The functionality that you'd like to see
  Specifically, can you clarify the credentials you would like to see using domain? I did a quick test and I'm noticing for Job credentials, that credential domains at the System level are being picked up, but all Folder credentials, both global and domain are not.

Expand comment: Martin Henschke added a comment - 2021-02-03 05:50, Edited by Martin Henschke - 2021-02-03 05:50

Martin Henschke added a comment - 2021-02-03 05:50 - edited Hi Javier, thanks for your report. Can you please add the following things to your request: Your usecase The functionality that you'd like to see Specifically, can you clarify the credentials you would like to see using domain? I did a quick test and I'm noticing for Job credentials, that credential domains at the System level are being picked up, but all Folder credentials, both global and domain are not.