[JIRA] (JENKINS-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-10-20 Thread dar...@ptgrey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darya A.Z. commented on  JENKINS-38581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
 Our Jenkins instance is very large with many plugins installed, it is impossible for us to install the plugins one by one and narrow this down. I tried to downgrade the subversion plugin to see if anything would change but the downgrade broke a few other plugins and I had to quickly revert back and install the latest version of subversion plugin. If it helps, I can provide you with the list of our plugins.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-10-18 Thread dar...@ptgrey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darya A.Z. commented on  JENKINS-38581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
 We're using Subversion Plug-in version 2.6  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-10-17 Thread dar...@ptgrey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darya A.Z. commented on  JENKINS-38581  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
 Thanks @mdonohue for your comment.  Attached is the screenshot of what we see in our Jenkins. Please note that  is missing at the beginning where the hyperlink should have been create (at least this is what we think is causing the issue).  Bug 1234$COMMIT_MESSAGE Please let me know if you need more info.  Thanks
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-10-17 Thread dar...@ptgrey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darya A.Z. updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38581  
 
 
  Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
Change By: 
 Darya A.Z.  
 
 
Attachment: 
 bugzilla_hyperlink.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-38581) Jenkins auto linkification for Bugzilla is broken on the build page

2016-09-28 Thread dar...@ptgrey.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Darya A.Z. created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38581  
 
 
  Jenkins auto linkification for Bugzilla is broken on the build page   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 mdonohue  
 
 
Components: 
 bugzilla-plugin  
 
 
Created: 
 2016/Sep/28 10:13 PM  
 
 
Environment: 
 Jenkins ver. 2.7.3  
 
 
Labels: 
 jenkins  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Darya A.Z.  
 

  
 
 
 
 

 
 On the job's main page, Recent Changes correctly link to Bugzilla bugs. However, if we go to specific builds' Recent Changes, links are broken.  On a build's page, something like the following is shown Bug 1234 - $COMMIT_MESSAGE which should have been like $LINK_TO_BUG1234 $COMMIT_MESSAGE From the page's source, it looks like all leading angled brackets are missing from the beginning of the Bugzilla URL's. For example Bug 1234$COMMIT_MESSAGE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] [security] (JENKINS-32956) Jenkins matrix-based security does not provide read-only access to project configurations

2016-02-15 Thread dar...@ptgrey.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darya A.Z. created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32956 
 
 
 
  Jenkins matrix-based security does not provide read-only access to project configurations  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 security 
 
 
 

Created:
 

 15/Feb/16 4:35 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Darya A.Z. 
 
 
 
 
 
 
 
 
 
 
According to the following, if I check mark the "Read" under "Job", I should be able to give read-only access to users.  https://wiki.jenkins-ci.org/display/JENKINS/Matrix-based+security  
However, selecting "Read" does not seem to provide read-only access to users. In fact, users do not have access to the job’s configuration page at all.  
I was wondering if I am missing anything here.  
Your feedback is much appreciated.Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment