Enable Jenkins Security Scan#389
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #389 +/- ##
=========================================
Coverage 71.80% 71.80%
Complexity 162 162
=========================================
Files 16 16
Lines 532 532
Branches 51 51
=========================================
Hits 382 382
Misses 124 124
Partials 26 26 ☔ View full report in Codecov by Sentry. |
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
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