The python plugin documentation points to an incorrect repository in its documentation page, which makes it difficult or impossible to evaluate whether there are any security issues with its implementation. At https://plugins.jenkins.io/python/ its github link is to https://github.com/jenkinsci/scp-plugin , an unrelated project.
Thanks for reporting the issue. The last commit on that repository from any maintainer of the plugin was over 9 years ago. The last release was 10 years ago. There are much simpler ways to use python in a Jenkins job without using that plugin (sh steps, powershell steps, bat steps).
In order to fix that issue, a new release of the plugin is required. That would need a maintainer willing to adopt the plugin and deliver a new release. I don't expect that to happen.
Mark Waite
added a comment - Thanks for reporting the issue. The last commit on that repository from any maintainer of the plugin was over 9 years ago. The last release was 10 years ago. There are much simpler ways to use python in a Jenkins job without using that plugin ( sh steps, powershell steps, bat steps).
In order to fix that issue, a new release of the plugin is required. That would need a maintainer willing to adopt the plugin and deliver a new release. I don't expect that to happen.
Unassigned
marvin greenberg
Votes:
1Vote for this issue
Watchers:
2Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Thanks for reporting the issue. The last commit on that repository from any maintainer of the plugin was over 9 years ago. The last release was 10 years ago. There are much simpler ways to use python in a Jenkins job without using that plugin (sh steps, powershell steps, bat steps).
In order to fix that issue, a new release of the plugin is required. That would need a maintainer willing to adopt the plugin and deliver a new release. I don't expect that to happen.