You can use launchctl to start
and stop
jenkins
$ To manually start the daemon: sudo launchctl load /Library/LaunchDaemons/org.jenkins-ci.plist
$ To manually stop the daemon: sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist
For more about launchctl
and install
see:
By default, Jenkins sets Content Security Policy for plugin pages. Allure requires less strict policy, you can set it via system property.
If you haven't done it before, add the following to Jenkins system properties configuration (you need to set both Hudson and Jenkins properties to make it works):
Jenkins script console (executes arbitrary script for administration/trouble-shooting/diagnostics) - http://localhost:8080/script , execute:
$ System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline';")
$ System.setProperty("jenkins.model.DirectoryBrowserSupport.CSP", "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline';")
You can read more about it in the Jenkins docs and find details in issue #715 in the Github repository of allure-core:
- Allure jenkins plugin docs: http://wiki.qatools.ru/display/AL/Allure+Jenkins+Plugin
- issue #715: allure-framework/allure1#715
- Jenkins docs: https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy
- Allure framework WIKI: https://github.com/allure-framework/allure-core/wiki