[JIRA] [envinject-plugin] (JENKINS-32708) Envinject plugin does not integrate correctly with role strategy plugin

2016-02-01 Thread mike.bayl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mike bayliss created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32708 
 
 
 
  Envinject plugin does not integrate correctly with role strategy plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Attachments:
 

 envinject+role.png 
 
 
 

Components:
 

 envinject-plugin, role-strategy-plugin 
 
 
 

Created:
 

 01/Feb/16 3:02 PM 
 
 
 

Environment:
 

 Jenkins 1.643, 1.646, Envinject plugin 1.92 or 1.92.1, role strategy plugin 2.2.0.   1.643 is an ubuntu 14 master with multiple windows/linux slaves, 1.646 is an ubuntu 14 master, with no slaves, assembled to isolate this bug.   Problem is visible in Firefox and Chrome.  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 mike bayliss 
 
 
 
 
 
 
 
 
 
 
When the envinject plugin is installed together with the role strategy plugin, the "Manage and Assign Roles" screen displays incorrectly. The column added to each role table for Env. Inject has no text in the second row of the table, and the third (and subsequent) row of the column includes the button for the "delete row" operation, not the checkbox for selecting the role. (Screenshot attached.) 
The probl

[JIRA] [build-failure-analyzer-plugin] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails

2014-11-12 Thread mike.bayl...@gmail.com (JIRA)














































mike bayliss
 commented on  JENKINS-17658


Provide a token so that build failure causes can be included in build failure emails















The token can be used in the default content box, so I presume that BFA is actually started by email-ext plugin in that case. 

I've looked at the code but java/groovy isn't my strong point and I can't work out how to start the BFA from the groovy template. If somebody can provide that information there isn't any need for code changes.



























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/d/optout.


[JIRA] [build-failure-analyzer] (JENKINS-24434) error text not highlighted if it has leading white space

2014-08-26 Thread mike.bayl...@gmail.com (JIRA)














































mike bayliss
 created  JENKINS-24434


error text not highlighted if it has leading white space















Issue Type:


Bug



Affects Versions:


current



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


26/Aug/14 8:55 AM



Description:


If the string matching an error begins with white space in the console log then it is not highlighted, and the indication link goes to the start of the console log even though the string is detected and reported on the build and project pages.

(This is NOT caused by the recent updates - it has been present since at least version 1.5.1 of the plugin.




Environment:


Ubuntu 12.04 (master and slaves)

Jenkins core 1.550

Build-failure-analyzer 1.9.1 




Project:


Jenkins



Priority:


Major



Reporter:


mike bayliss

























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/d/optout.