[JIRA] (JENKINS-58372) Unable to update Jira Issues with Pipeline

2019-10-01 Thread tim.t.pres...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tim Preston commented on  JENKINS-58372  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to update Jira Issues with Pipeline   
 

  
 
 
 
 

 
 Similar result on Jenkins 2.164.3 + Git Plugin 4.0.0-rc + JIRA Plugin 3.0.7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] [subversion-plugin] (JENKINS-19600) Subversion Plugin 1.51 consistently throws NoSuchMethodError

2015-11-09 Thread tim.t.pres...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Preston commented on  JENKINS-19600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion Plugin 1.51 consistently throws NoSuchMethodError  
 
 
 
 
 
 
 
 
 
 
Manuel Jesús Recena Soto, that's fine by me. I haven't encountered this issue for quite some time now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-pipeline-plugin] (JENKINS-21188) Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users

2015-05-06 Thread tim.t.pres...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Preston commented on  JENKINS-21188 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users  
 
 
 
 
 
 
 
 
 
 
Experiencing this issue with plugin 1.4.7 on Jenkins 1.609 and we're using Project-based Matrix Authorization Strategy for security. When experiencing this issue, however, all my users see is a blank Jenkins screen (no jobs listed) when accessing the default system All view, not a stacktrace. The stacktrace is only seen in the system logs (for example: http://pastebin.com/7snZ838E). 
Since I need to have the plugin installed, the only way that I've been able to get around the issue is to NOT create global Build Pipeline views and only have the users create private Build Pipeline views, if needed. 
The gist of the problem seems to be: If 

any
 global Build Pipeline views exist and the current user does not have access to a job in any of the views, they will get the blank Jenkins screen. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [build-pipeline-plugin] (JENKINS-21188) Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users

2015-05-06 Thread tim.t.pres...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim Preston commented on  JENKINS-21188 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access project for not-logged in users  
 
 
 
 
 
 
 
 
 
 
The user 

is
 logged in, they just don't have access to that particular job. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-16777) ArrayIndexOutOfBoundsException when trying to publish the Jacoco report

2013-02-13 Thread tim.t.pres...@gmail.com (JIRA)














































Tim Preston
 commented on  JENKINS-16777


ArrayIndexOutOfBoundsException when trying to publish the Jacoco report















It fixed the problem for me when I entered something in the "Inclusions" section.  However, I'm not too excited about having to fill this parameter in on 100+ jobs.

Tim



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
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/groups/opt_out.




[JIRA] (JENKINS-15242) org.objectweb.asm.ClassReader.accept error

2012-10-08 Thread tim.t.pres...@gmail.com (JIRA)














































Tim Preston
 commented on  JENKINS-15242


org.objectweb.asm.ClassReader.accept error















I just installed 1.0.7 (first time installing this plugin).  I'm still getting the same error.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira