Skip to content

Commit 759ee92

Browse files
authored
Explain the deprecation of the MongoDB plugin (#83)
Update this documentation because it is used to create the documentation on plugins.jenkins.io
1 parent 306007c commit 759ee92

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

content/JENKINS/MongoDB-Plugin.html

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,19 @@ <h1 id="title-heading" class="pagetitle">
5959

6060
</div></div>
6161

62+
<h3>Deprecated</h3>
63+
64+
The plugin has been deprecated because it can no longer perform its primary function of downloading and installing MongoDB for a freestyle job.
65+
66+
MongoDB does not allow the Jenkins tool installer list generator to list their available community editions. It has been disallowed since at least November, 2022.
67+
68+
Since we can't list their available community editions from our list generator, that tool installer data will always be empty.
69+
That blocks the primary use case of the plugin
70+
71+
The plugin also has a <a href="https://www.jenkins.io/security/advisory/2020-09-16/#SECURITY-1904">known security vulnerability</a>.
72+
73+
As noted in <a href="https://issues.jenkins.io/browse/JENKINS-76359">JENKINS-76359</a>, the MongoDB tool installer file has been empty since November 29, 2022.
74+
The primary function of the MongoDB plugin is to provide an installer for MongoDB that can be used from a freestyle project, but the empty tool installer file means that function has not been provided for over 3 years.
6275

6376
<p>This plugin provides <a href="http://www.mongodb.org/" class="external-link" rel="nofollow">MongoDB</a> integration capabilities.</p>
6477

0 commit comments

Comments
 (0)