Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No css in the report showed in jenkins (easy to fix) #403

Closed
sbuisson opened this issue Sep 26, 2017 · 3 comments
Closed

No css in the report showed in jenkins (easy to fix) #403

sbuisson opened this issue Sep 26, 2017 · 3 comments

Comments

@sbuisson
Copy link
Contributor

Hello:
Can you place the css of the html report in separated file?

Jenkins have a functionality who allow to archive some part of the workspace as "artifact" ( who will easier to access than if they stay in the workspace- something tricky if you use pipeline-).

I want this functionality with pitest, in order to display the pitest-report
The issue is that jenkins forbid "style-src self" for this archived file. (aka the css class definition in the html)

Can you place the css of the html report in separated file?

the stack trace:

Refused to apply inline style because it violates the following Content Security Police directive: "style-src 'self'"

@hcoles
Copy link
Owner

hcoles commented Oct 23, 2017

Should be fixed in next release thanks to PR from @kiftio

@hcoles
Copy link
Owner

hcoles commented Nov 29, 2017

released in 1.2.5

@hcoles hcoles closed this as completed Nov 29, 2017
@dalewking
Copy link

I am actually having the opposite problem. CSS is not loading in Jenkins because it is in a separate file. My issue is not the CSP but because the content of the Jenkins instance requires authentication and the call to get the CSS doesn't pass along the authentication cookies I get 403 error trying to retrieve the CSS. So I am looking for a solution to inline the CSS. Might be nice to make it an option whether to inline or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants