The Jenkins project takes security seriously. We make every possible effort to ensure users can adequately secure their automation infrastructure. To that end, we work with Jenkins core and plugin developers, as well as security researchers, to fix security vulnerabilities in Jenkins in a timely manner, and to improve the security of Jenkins in general.
We as plugin developers should try our best to support this. One way of doing so is to enable the Jenkins Security Scan on this repository. For more details see the documentation.
This PR may create new issues in the Code scanning section of this project once it is merged. I'd be happy to try and help resolve those if necessary.
Please note this PR was created semi-automatically. If you find any issue with it, don't hesitate to ping me.For more details see the Jenkins Developers Google Group.
Submitter checklist
[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue
It is stated in the
JENKINS SECURITY POLICYthatWe as plugin developers should try our best to support this. One way of doing so is to enable the Jenkins Security Scan on this repository. For more details see the documentation.
This PR may create new issues in the Code scanning section of this project once it is merged. I'd be happy to try and help resolve those if necessary.
Please note this PR was created semi-automatically. If you find any issue with it, don't hesitate to ping me. For more details see the Jenkins Developers Google Group.
Submitter checklist