Do a chmod 777 on the exploded war ,i.e., *.jenkins*. It will work, I m
using jenkins 1.578 on Solaris10.
On Thursday, November 7, 2013 at 7:14:51 AM UTC+5:30, thejo...@gmail.com
wrote:
>
> Hi,
> I used to be able to run jenkins.war on solaris 10 using:
> $JAVA_HOME/bin/java -jar $JENKINS_HOME
Did you find answer to your question? I am facing the exact same issue
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.
Hi,
I used to be able to run jenkins.war on solaris 10 using:
$JAVA_HOME/bin/java -jar $JENKINS_HOME/jenkins.war --httpPort=8081
This worked fine up till Jenkins version 1.535, so I assume the
introduction of Jetty had something to do with this issue.
Jenkins still starts fine and the logs are th
