infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-14650) Change Jenkins Content Security Policy
Date Sun, 23 Jul 2017 00:50:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-14650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097469#comment-16097469
] 

Gavin commented on INFRA-14650:
-------------------------------

Ok patch pushed to a branch, once that has been merged to deployment we'll need to schedule
downtime for a Jenkins restart. So it could be a few days before we see this fixed in place
unless an unscheduled restart occurs before then.

> Change Jenkins Content Security Policy
> --------------------------------------
>
>                 Key: INFRA-14650
>                 URL: https://issues.apache.org/jira/browse/INFRA-14650
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Steve Rowe
>            Assignee: Gavin
>
> The Lucene project is encountering issues with browsers not invoking CSS/JS on Jenkins-produced
and -served content (e.g. javadocs), apparently because of Content Security Policy.  This
has happened before: INFRA-11746 .
> Here are current examples of the problem: https://builds.apache.org/view/L/view/Lucene/job/Solr-reference-guide-master/javadoc/
and https://builds.apache.org/view/L/view/Lucene/job/Solr-Artifacts-7.0/javadoc/solr-core/index.html
.
> Can the same changes made under INFRA-11746 be re-applied?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message