I agree with Jesse that we should avoid jenkins.py if possible. Python Jenkins is a possible option. Also, it might be possible to add some integrations with Python development tools in Jenkins. https://jenkins.io/solutions/python/ references only few plugins, but actually there are many plugins more:
- https://github.com/jenkinsci/python-plugin - https://plugins.jenkins.io/pyenv - https://plugins.jenkins.io/pyenv-pipeline - https://plugins.jenkins.io/shiningpanda - https://plugins.jenkins.io/robot PyEnv, Robot Framework and Shining Panda plugins seem to be more or less active (<6 months since the last release). Also, there could be some integrations between Python tools and the new Warnings Ng plugin. BR, Oleg On Wednesday, January 9, 2019 at 4:36:53 PM UTC+1, Jesse Glick wrote: > > On Wed, Jan 9, 2019 at 10:19 AM Vu Tuan Pham <[email protected] > <javascript:>> wrote: > > https://github.com/jenkinsci/jenkins.py > > Please do not advertise this. We had to officially deprecate the Ruby > plugin bindings because it was a security & maintainability headache. > AFAICT the only usage of this wrapper is > > > https://github.com/jenkinsci/installshield-plugin/tree/master/src/main/python > > and it would be great to able to rewrite that in Java and retire this > binding too. > > (python-jenkins sounds harmless, as that is running in a separate > client process.) > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd845a13-09f4-4c72-b979-64d70b0a3f5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
