Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32118

Document Jenkins security settings so Robot Framework log/report can be opened

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • robot-plugin
    • None
    • Jenkins 1.642, Robot Framework plugin 1.6.2
    • 2.1.2

      When trying to open Robot Framework log (or report) I get an error in my browser:
      "...
      Opening Robot Framework log failed

      Verify that you have JavaScript enabled in your browser.
      Make sure you are using a modern enough browser. Firefox 3.5, IE 8, or equivalent is required, newer browsers are recommended.
      Check are there messages in your browser's JavaScript error log. Please report the problem if you suspect you have encountered a bug.
      ..."

      I am using Firefox v. 43 where javascript.enabled is true.

       

      EDIT:

      Per danielbeck in this comment, a possible solution to study is used in Cucumber-plugin: https://github.com/jenkinsci/cucumber-reports-plugin/pull/66/files

        1. Selection_243.png
          Selection_243.png
          33 kB
        2. JENKINS-32118.png
          JENKINS-32118.png
          19 kB

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

          Roman Solus created issue -
          Oleg Nenashev made changes -
          Component/s New: robot-plugin [ 15773 ]
          Component/s Original: _unsorted [ 19622 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ] New: jpiironen [ jpiironen ]

          martino tu added a comment -

          Same issue for me.

          martino tu added a comment - Same issue for me.

          Bob Lafortune added a comment -

          Same thing here

          Bob Lafortune added a comment - Same thing here

          Zeebee Z added a comment -

          On my chrome, 47.0.2526.106 m, the same bug

          Zeebee Z added a comment - On my chrome, 47.0.2526.106 m, the same bug

          Alexei Margasov added a comment -

          The bug appeared after I updated version jenkins from 1.616 to 1.625.3

          Alexei Margasov added a comment - The bug appeared after I updated version jenkins from 1.616 to 1.625.3

          Daniel Beck added a comment -

          This is likely a result of the security content in Jenkins 1.625.3 and 1.641:

          https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09
          https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy

          Daniel Beck added a comment - This is likely a result of the security content in Jenkins 1.625.3 and 1.641: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09 https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy

          Bob Lafortune added a comment -

          Has suggested by the links provided, I was able to get around the issue by adding:
          java -Dhudson.model.DirectoryBrowserSupport.CSP= -jar jenkins.war

          In my service startup file.

          Bob Lafortune added a comment - Has suggested by the links provided, I was able to get around the issue by adding: java -Dhudson.model.DirectoryBrowserSupport.CSP= -jar jenkins.war In my service startup file.

          Jhonny Peppy added a comment -

          Same issue from Jenkins ver. 1.643.

          Jhonny Peppy added a comment - Same issue from Jenkins ver. 1.643.

            aleksisimell Aleksi Simell
            romek_es Roman Solus
            Votes:
            51 Vote for this issue
            Watchers:
            68 Start watching this issue

              Created:
              Updated:
              Resolved: