Skip to content

Commit 6f41db3

Browse files
authored
Explain why Jira is needed despite GH issue tracking (#5368)
Co-authored-by: Daniel Beck <[email protected]>
1 parent 40ddcd0 commit 6f41db3

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

content/doc/developer/publishing/preparation.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,4 +34,6 @@ See link:../documentation[Documentation] for more information.
3434

3535
Jenkins plugins distributed via Jenkins project update sites need to be hosted in the https://github.com/jenkinsci[jenkinsci GitHub organization], so you will need a user account on GitHub.
3636

37-
To actually release your plugin, you will need a https://accounts.jenkins.io[Jenkins community account] that will give you access to the https://issues.jenkins.io/[issue tracker] and https://repo.jenkins-ci.org/[Maven repository].
37+
To actually release your plugin, you will need a https://accounts.jenkins.io[Jenkins community account] that will give you access to the https://issues.jenkins.io/[Jira issue tracker] and https://repo.jenkins-ci.org/[Maven repository].
38+
39+
Even if you choose to track your plugin's issues on GitHub, link:/security/for-maintainers/[you may be assigned security vulnerabilities in your plugin in Jira].

0 commit comments

Comments
 (0)