-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins core >= 2.226 (2020-03-15), see https://github.com/jenkinsci/jenkins/pull/4546 for more details
-
-
script-security 1.74
I think this plugin should show up in category "Security" in "Manage Jenkins" page of modern Jenkins releases (currently it is "Uncategorized"):
- implementation in analogy to e.g. https://github.com/jenkinsci/credentials-plugin/compare/credentials-2.3.3...credentials-2.3.4 or https://github.com/jenkinsci/configuration-as-code-plugin/pull/1358
- see https://github.com/jenkinsci/jenkins/pull/4546 for more background
- try to use ManagementLink.Category.SECURITY?
Should be a rather low-hanging fruit...
- links to
[JENKINS-61927] Add category to system settings for modern Jenkins releases
Reinhold Füreder
created issue -
Reinhold Füreder
made changes -
| Description |
Original:
I think this plugin should show up in category "Security" in "Manage Jenkins" page of modern Jenkins releases (currently it is "Uncategorized"): * implementation in analogy to e.g. https://github.com/jenkinsci/credentials-plugin/compare/credentials-2.3.3...credentials-2.3.4 or https://github.com/jenkinsci/configuration-as-code-plugin/pull/1358 * see https://github.com/jenkinsci/jenkins/pull/4546 for more background * try to use {{ManagementLink.Category.SECURITY}}? |
New:
I think this plugin should show up in category "Security" in "Manage Jenkins" page of modern Jenkins releases (currently it is "Uncategorized"): * implementation in analogy to e.g. https://github.com/jenkinsci/credentials-plugin/compare/credentials-2.3.3...credentials-2.3.4 or https://github.com/jenkinsci/configuration-as-code-plugin/pull/1358 * see https://github.com/jenkinsci/jenkins/pull/4546 for more background * try to use {{ManagementLink.Category.SECURITY}}? Should be a rather low-hanging fruit... |
Reinhold Füreder
made changes -
| Assignee | New: Devin Nusbaum [ dnusbaum ] |
reinholdfuereder Yeah, I did not realize that a ticket had been filed for this issue, thanks! This should be fixed in Script Security 1.74 and newer on Jenkins 2.226 and newer.
| Released As | New: script-security 1.74 | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Remote Link | New: This issue links to "jenkinsci/script-security-plugin#302 (Web Link)" [ 25302 ] |
Reinhold Füreder
added a comment - dnusbaum Thanks nonetheless for fixing!
I have a naive suspicion WRT overlooking this ticket:
- As I have commented on some tickets, I also seemingly do not get email notifications for Jenkins tickets (from JIRA) anymore, e.g. also not for your aforementioned comment from yesterday!
- And our admin just checked that e.g. on 20 May 2020 our mail server logged that your mail server (IP) was black listed (partially) or so... And the same IP is still partially blacklisted with respect to mail sending...
Reinhold Füreder
added a comment - dnusbaum Thanks nonetheless for fixing!
I have a naive suspicion WRT overlooking this ticket:
As I have commented on some tickets, I also seemingly do not get email notifications for Jenkins tickets (from JIRA) anymore, e.g. also not for your aforementioned comment from yesterday!
And our admin just checked that e.g. on 20 May 2020 our mail server logged that your mail server (IP) was black listed (partially) or so... And the same IP is still partially blacklisted with respect to mail sending...
reinholdfuereder Thanks, but no the issue is just that I do not have notifications set up for newly filed issues and unfortunately do not have time to triage filed issues on a regular basis.
dnusbaum Hm, OK. But again I have not received a notification for this last comment by you – as I am certain was always the case in the past (that may be several months ago):
- Therefore I have now naively tried to change my profile settings with respect to "Autowatch" from "Inherit from global settings" to "Enabeld" (Because it says "Issues that you create or comment on will automatically be watched for future changes.") – which I never changed in the past...
- Or are maybe default notifications only happening when using the "@<USER>"? And am I mixing up things due to Alzheimer?
- Oh no, there was a "@<USER>" in your comment (where I have not received a notification so far)
- Oh no, there was a "@<USER>" in your comment (where I have not received a notification so far)
Reinhold Füreder
added a comment - - edited dnusbaum Hm, OK. But again I have not received a notification for this last comment by you – as I am certain was always the case in the past (that may be several months ago):
Therefore I have now naively tried to change my profile settings with respect to "Autowatch" from "Inherit from global settings" to "Enabeld" (Because it says "Issues that you create or comment on will automatically be watched for future changes.") – which I never changed in the past...
Or are maybe default notifications only happening when using the "@<USER>"? And am I mixing up things due to Alzheimer?
Oh no, there was a "@<USER>" in your comment (where I have not received a notification so far)
I think you (dnusbaum) just fixed and released that via v1.74 and https://github.com/jenkinsci/script-security-plugin/pull/302?