[JIRA] (JENKINS-32118) Document Jenkins security settings so Robot Framework log/report can be opened

2 views
Skip to first unread message

subodh2691@gmail.com (JIRA)

unread,
Apr 24, 2018, 9:58:03 AM4/24/18
to jenkinsc...@googlegroups.com
Subodh Agnihotri commented on Bug JENKINS-32118
 
Re: Document Jenkins security settings so Robot Framework log/report can be opened

Still facing the issue in Jenkins ver. 2.107.2 for opening report.html of Robot framework.
Log.html file is coming after workaround suggested, but report.html still displays the same error

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

subodh2691@gmail.com (JIRA)

unread,
Apr 24, 2018, 9:59:05 AM4/24/18
to jenkinsc...@googlegroups.com

tatu.kairi@eficode.com (JIRA)

unread,
Aug 14, 2018, 9:06:03 AM8/14/18
to jenkinsc...@googlegroups.com
Tatu Kairi commented on Bug JENKINS-32118
 
Re: Document Jenkins security settings so Robot Framework log/report can be opened

Subodh Agnihotri the workaround thus work, though. I'd suggest you double check have you employed it correctly.

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

subodh2691@gmail.com (JIRA)

unread,
Aug 15, 2018, 7:48:08 AM8/15/18
to jenkinsc...@googlegroups.com

Yeah it worked. There was a caching issue which was resolved later. I will mark this closed

subodh2691@gmail.com (JIRA)

unread,
Aug 15, 2018, 7:48:15 AM8/15/18
to jenkinsc...@googlegroups.com
Subodh Agnihotri closed an issue as Fixed
 
Change By: Subodh Agnihotri
Status: Reopened Closed
Resolution: Fixed

tatu.kairi@eficode.com (JIRA)

unread,
Aug 15, 2018, 8:18:05 AM8/15/18
to jenkinsc...@googlegroups.com
Tatu Kairi reopened an issue
 

Should not have been closed to begin with

Change By: Tatu Kairi
Resolution: Fixed
Status: Closed Reopened
Assignee: Tarik  Remous jpiironen

tatu.kairi@eficode.com (JIRA)

unread,
Aug 15, 2018, 8:18:10 AM8/15/18
to jenkinsc...@googlegroups.com
Tatu Kairi commented on Bug JENKINS-32118
 
Re: Document Jenkins security settings so Robot Framework log/report can be opened

Subodh Agnihotri This is not your issue, why on earth do you think you can close it?!

tatu.kairi@eficode.com (JIRA)

unread,
Aug 15, 2018, 8:21:02 AM8/15/18
to jenkinsc...@googlegroups.com
Tatu Kairi edited a comment on Bug JENKINS-32118
[~subodh2691] the workaround thus does work, though. I'd suggest you double check have you employed it correctly.

dineshnaik.dj@gmail.com (JIRA)

unread,
Sep 12, 2019, 2:31:05 AM9/12/19
to jenkinsc...@googlegroups.com
Dinesh J commented on Bug JENKINS-32118

does anybody have permanent solution for this? I can able to resolve this as temporary by adding following in the script console in manage Jenkins System.setProperty("hudson.model.DirectoryBrowserSupport.CSP","sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ;") but every time Jenkins server restart changes disappeared. any permanent solution for this?

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

grimbeaj@gmail.com (JIRA)

unread,
Sep 12, 2019, 5:57:06 PM9/12/19
to jenkinsc...@googlegroups.com

My team gave up on doing the work around. We just shuffle the robot logs off to a different storage static web host, along with a lot of logs that Jenkins doesn't capture for us anyway.

 

 

Reply all
Reply to author
Forward
0 new messages