Add Jenkins security scan to common files #597
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timja
approved these changes
Mar 2, 2023
Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>
timja
approved these changes
Mar 2, 2023
|
@jglick Mind cutting a release, please? |
|
https://github.com/jenkinsci/archetypes/releases/tag/archetypes-1.18 I somehow botched the commit history a bit but |
|
Thanks!
… On 3. Mar 2023, at 03:29, Jesse Glick ***@***.***> wrote:
https://github.com/jenkinsci/archetypes/releases/tag/archetypes-1.18
I somehow botched the commit history a bit but maven-release-plugin 🤷
—
Reply to this email directly, view it on GitHub <#597 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADGDOVPLKU3WVOW7CVZZJHLW2FJPLANCNFSM6AAAAAAVNXGQNY>.
You are receiving this because you modified the open/close state.
|
daniel-beck
reviewed
Mar 3, 2023
| @@ -0,0 +1,23 @@ | |||
| # More information about the Jenkins security scan can be found at the developer docs: https://www.jenkins.io/doc/developer/security/scan/ | |||
There was a problem hiding this comment.
Please reference https://www.jenkins.io/redirect/jenkins-security-scan/ from outside jenkins.io for URL stability.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New hosting requests are reviewed initially by our set of predefined CodeQL rules. The recent hosting requests subject to the new scanning showed long lists of issues (including a few false-positives).
Therefore, I'm assuming a lack of awareness of how to mitigate, and even better, avoid introducing possible security vulnerabilities in your plugin.
For this reasoning, I would like to include the security scan by default in all new plugins, to raise awareness of possible security issues and give maintainers an opportunity, to react to issues.