[JIRA] (JENKINS-62235) Default Credentials not used - Authentication failure

2020-05-10 Thread 'dominik.jess...@chello.at (JIRA)' via Jenkins Issues 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Jessich assigned an issue to Kristy Hughes  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-62235  
 
 
  Default Credentials not used - Authentication failure   
 

  
 
 
 
 

 
Change By: 
 Dominik Jessich  
 
 
Assignee: 
 Kristy Hughes  
 

  
 
 
 
 

 
 
 

 
 
 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.206176.1589149087000.24376.1589149260187%40Atlassian.JIRA.

[JIRA] (JENKINS-62235) Default Credentials not used - Authentication failure

2020-05-10 Thread 'dominik.jess...@chello.at (JIRA)' via Jenkins Issues 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Jessich created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-62235  
 
 
  Default Credentials not used - Authentication failure   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins_global_settings_bitbucket_instance.png, jenkins_multibranch_pipeline_scan_output.png, jenkins_multibranch_pipeline_settings_bitbucket_repository.png  
 
 
Components: 
 atlassian-bitbucket-server-integration-plugin  
 
 
Created: 
 2020-05-10 22:18  
 
 
Environment: 
 Jenkins 2.222.3 (installed with RPM using Jenkins YUM repositories)  Bitbucket Server 7.2.1  Bitbucket Server Integration Plugin 1.1.0  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Dominik Jessich  
 

  
 
 
 
 

 
 As the plugin documentation from within Jenkins states, when username with password credentials (for build auth) are selected as default for Bitbucket Instance in Jenkins configuration, users are not required to select them and the "global" ones will be used by default. However, leaving the corresponding field for credentials (for build auth) empty in a Multibranch Pipeline Job configuration, results in authentication failure in Bitbucket Server. The repository cannot be scanned, because repository cannot be accessed. This means a core functionality is broken with current plugin version (see environment description). Blocks all users to create a job to checkout from Bitbucket themselves. Workaround: As the admin privileges are required to use the credentials, Jenkins admin needs to select the correct credentials for each job configuration.