[JIRA] (JENKINS-55915) Invalid refspec

2019-02-01 Thread kevin.johns...@elevatetickets.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Johnsrud commented on  JENKINS-55915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invalid refspec   
 

  
 
 
 
 

 
 Sort of, I actually now think this is an issue with the multiple SCMs plugin that I'm using. It's auto-populating some advanced settings and/or reading config information. When I remove that it works fine. As soon as I add it back, even with correct settings it throws the same stack trace. I know this plugin in deprecated so I guess it's time to move to pipelines for some of these simple projects to support multiple SCMs.  
 

  
 
 
 
 

 
 
 

 
 
 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-55915) Invalid refspec

2019-02-01 Thread kevin.johns...@elevatetickets.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Johnsrud commented on  JENKINS-55915  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Invalid refspec   
 

  
 
 
 
 

 
 Sort of, I actually now think this is an issue with the multiple SCMs plugin that I'm using. It's auto-populating some advanced settings and/or reading config information. When I remove that it works fine. As soon as I add it back, even with correct settings it throws the same stack trace. I know this plugin in deprecated so I guess it's time to move to pipelines for some of these simple projects to support multiple SCMs.  
 

  
 
 
 
 

 
 
 

 
 
 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-55915) Invalid refspec

2019-02-01 Thread kevin.johns...@elevatetickets.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Johnsrud created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55915  
 
 
  Invalid refspec   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 System Information [Jenkins].pdf  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2019-02-01 15:54  
 
 
Environment: 
 Dockerized Jenkins 2.150.2 (pulled from docker repo)  Browser: Chrome (mac) Version 72.0.3626.81  (see attached systeminfo)   
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kevin Johnsrud  
 

  
 
 
 
 

 
 Just recently started seeing this when I attempt to edit projects. This thing is when I go into edit the configuration the git portion updates itself automatically briefly displaying some red text and then resetting one of my git entries in my project. I've tried clearing the wildcards in my entries and saving but it still won't apply and gives the same stack trace every time. I verified I was running the latest plugins and LTS version to make sure it wasn't a bug in older software. When I set everything back to how it was and hit save or if I just hit apply with making no changes I get this exception error. I tried reverting to an older build version in case some change made to the entry caused this but it continues to occur even if I revert to an older version. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant p