Anyway, Jenkins has no other good user interface except the web interface. HTTP is very easily proxyable, so usually accessing the Jenkins web interface is not a problem. During the few years I've used Jenkins, you are the first who is requesting some other way to access Jenkins.
Another popular way to use Jenkins is to configure Jenkins to send email. If the email has all the details of the build failure, this should pretty much eliminate the need to ever visit the web interface. Another idea (already suggested by an earlier poster) is to set up Jenkins in a non-restricted network where you can access it. If building and testing must happen in a restricted network, set up Jenkins slaves into the restricted network and configure the builds and test to happen on the slaves. That's actually what I do at work. The restricted network is reachable by first logging (using ssh) to a server from which you can log into the test server in the restricted network. I use the "Launch slave via execution of command on the master" and the command is: ssh server1 ssh server2 java -jar slave.jar. -- Sami 2012/6/19 louwho <louels...@comcast.net>: > I must not have stated the previous message correctly. When logged on to > the host machine, I can use the web interface to access the Jenkins service > on the VM...but I cannot do this from any other system. > > On Thursday, June 14, 2012 5:50:55 PM UTC-4, louwho wrote: >> >> Is there (or should there be), a seperate forum\group\whatever for those >> who have questions regarding Jenkins installed as a windows Service? Also, >> is there a plugin (to be installed on a windows system) for monitoring >> Jenkins jobs? I understand that CCTray can be used, but it only monitors >> (cannot kick off a build).
