[JIRA] [htmlpublisher-plugin] (JENKINS-32054) can not autoindex the index.html file

2015-12-15 Thread esch...@sumtotalsystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ernst Schepp commented on  JENKINS-32054 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: can not autoindex the index.html file  
 
 
 
 
 
 
 
 
 
 
Windows Server 2008, Jenkins 1.636, htmlpublisher-plugin 1.8. 
I upgraded to Jenkins 1.642 and htmlpublisher-plugin 1.10. 
I now only see "very simple" Reports (html only documents). All other references in the page are no longer work (if the page refers to css, xsl, any Iframe references or .js).  This renders the system useless to us, not being able to see any of the historical or new report vi the Jenkins interface (can only “see” them when logged into the Jenkins master server and going into the htmlreports folder for the job on the drive). 
I had to revert Jenkins back to 1.636 and the htmlpublisher-plugin to 1.8 to get back to a working state.  It looks like the Jeninks security changes in combination with the htmlpublisher-plugin will not allow pages to be rendered properly anymore.  
I did not try the “-Dhudson.model.DirectoryBrowserSupport.CSP="script-src 'unsafe-inline' reference in the Jenkins.xml file (since I already reverted everything). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again

2015-06-04 Thread esch...@sumtotalsystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ernst Schepp commented on  JENKINS-28316 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again  
 
 
 
 
 
 
 
 
 
 
Thanks Antoine!  I will try it out as soon as it is ready for download in the Plugin Manager. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [fitnesse-plugin] (JENKINS-28316) Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again

2015-05-08 Thread esch...@sumtotalsystems.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ernst Schepp created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28316 
 
 
 
  Publish Fitnesse results - fails on 1.12 - reverted to 1.8 - works again  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 fitnesse-plugin 
 
 
 

Created:
 

 08/May/15 6:18 PM 
 
 
 

Environment:
 

 Windows (master and slave)  Jenkins version 1.611  Windows (Server 2008) 
 
 
 

Labels:
 

 plugin fitnesse 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Ernst Schepp 
 
 
 
 
 
 
 
 
 
 
Upgraded my Jenkins instance (to version 1.611). Tried to upgrade fitnesse plugin also from 1.8 to 1.12. 
Results from version 1.2 (works) ... Reading results as windows-1252 from D:\WS\master\Reports\fitnesse\fitnesse_results.xml Parsing results...  Got results: null (): 1650 right, 0 wrong, 0 ignored, 0 exceptions Archiving artifacts . 
Build fails on Version 1.13: Reading results as windows-1252 from D:\WS\master\Reports\fitnesse\fitnesse_results.xml Parsing results...  Write fitnesse results to: D:\Apps\Jenkins\jobs\Master 

[JIRA] [xtrigger] (JENKINS-18803) Null pointer crash when enabling any of the trigger from xTrigger plug-in

2013-07-31 Thread esch...@sumtotalsystems.com (JIRA)














































Ernst Schepp
 commented on  JENKINS-18803


Null pointer crash when enabling any of the trigger from xTrigger plug-in















Some corrections on my comment:

I' on Jenkins ver. 1.525
It "looked" as if the downgrade worked - but this was not true.
I could save the jobs with no errors - but the trigger would not trigger a build.
Had to downgrade Jenkins to the previous version (Jenkins ver. 1.499) and installed the (URL Trigger plug-in 0.31).
This "looks" like it is working again.
Please fix to work with latest version of Jenkins. 



























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] [xtrigger] (JENKINS-18803) Null pointer crash when enabling any of the trigger from xTrigger plug-in

2013-07-30 Thread esch...@sumtotalsystems.com (JIRA)














































Ernst Schepp
 commented on  JENKINS-18803


Null pointer crash when enabling any of the trigger from xTrigger plug-in















I have the same issue.
The issue is with URLTrigger Plugin 0.31 that shows up as :Release 0.21" on https://wiki.jenkins-ci.org/display/JENKINS/URLTrigger+Plugin

I downgraded to 0.30 and I was able to save jobs again.



























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-12012) Atomatic upgrade link is no longer available on Manage Jenkins Page

2013-01-15 Thread esch...@sumtotalsystems.com (JIRA)














































Ernst Schepp
 commented on  JENKINS-12012


Atomatic upgrade link is no longer available on Manage Jenkins Page















To get around the issue I had to:

	do the "Downgrade" option (Restore the previous version of Jenkins).
	then use the Automatic Upgrade option to a newer version.
Now the "Or Upgrade Automatically" button is again available.



You could close this issue now.



























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