One of the ways to achieve this is through making changes in the jenkins.xml file, which is located in your main Jenkins installation to permanently changing the Content Security Policy when Jenkins is running as a Windows Service. Thus after making the changes, our report will look at something as shown in Figure 2:įigure 2: Properly formatted Newman report after modifying Jenkins’s Content Security Policy While turning this policy off completely is not recommended, it can be beneficial to adjust the policy to be less restrictive, allowing the use of external reports without compromising security. Therefore it requires modifying the CSP to see the visually-appealing version of the Newman report. Thus with the default policy, our report will look something like this This can cause problems with content added to Jenkins via build processes, typically using the Plugin. The default policy blocks pretty much everything – no JavaScript, inline CSS, or even CSS from external websites. to send Content Security Policy (CSP) headers which describes how certain resources can behave. This is due to one of the security features of Jenkins i.e. If you notice, the test execution Newman report generated after Jenkins build execution looks something as shown in Figure 1:įigure 1: Report in plain format due to Jenkins’s default security policy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |