[JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL

2018-11-21 Thread meise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark isert edited a comment on  JENKINS-38664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: bitbucket source plugin fails with bad URL
 

  
 
 
 
 

 
 I was getting this error as well.  After adding some logging in the plugin I discovered here:        if (cfg == null || cfg.getUrl() == null)  {  {             LOGGER.fine(Level.INFO, "JenkinsLocationConfiguration empty");              throw new IllegalStateException("Could not determine Jenkins URL.");          }That the server URL required a "." in it.  In our case the Jenkins URL was a short name without a ".".  So I changed it to use a long URL alias we have as well.  This seems like a bug.  At the least there could be more logging added to the code .    I had to add more logging to figure this out for example and the original exception stack trace wasn't logged in this case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL

2018-11-21 Thread meise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark isert commented on  JENKINS-38664  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: bitbucket source plugin fails with bad URL
 

  
 
 
 
 

 
 I was getting this error as well.  After adding some logging in the plugin I discovered here:         if (cfg == null || cfg.getUrl() == null)  {             LOGGER.fine(Level.INFO, "JenkinsLocationConfiguration empty");             throw new IllegalStateException("Could not determine Jenkins URL.");         } That the server URL required a "." in it.  In our case the Jenkins URL was a short name without a ".".  So I changed it to use a long URL alias we have as well.  This seems like a bug.  At the least there could be more logging added to the code   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.