The two topics of your question seem to be the command line interface and REST API. They seem to be almost independent questions to me.
Can you explain further why you care how the command line interface is implemented? It seems that if you need a command line interface, you will call it from a command line, so it will be a "black box" to you and you won't care about the internal API. You wouldn't need to know which API it uses internally to send requests to the Jenkins server, since you're calling it from the command line. The Jenkins command line is one command line option: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI If instead you want to control Jenkins from your favorite programming language, then an implementation in that programming language is probably even easier to use than a REST implementation. Python Jenkins is an option (if you program in Python): http://packages.python.org/python-jenkins/ A Ruby Jenkins interface (if you program in Ruby): https://github.com/john-griffin/jenkins-client A Node.js interface (as you mentioned): https://wiki.jenkins-ci.org/display/JENKINS/Nestor I'm sure there are others. Mark Waite >________________________________ > From: Bharathi Ramalingam <ramalingam.bhara...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Tuesday, December 11, 2012 6:40 AM >Subject: Jenkins CLI using REST APIs > > >Hi All, > I am looking for cli for Jenkins using RESTful APIs. I have seen >different cli implementations like, >https://wiki.jenkins-ci.org/display/JENKINS/Nestor >http://packages.python.org/autojenkins/intro.html >and in-build cli also. >But none of them suits my need. >Please point me if there is any cli implemented using Rest Apis. > >Thanks, > > >
