I have not seen a response to this, but I wanted to post my solution.
It may not be fitting for all, but it's definitely a working setup for
us.
We ended up leaving Jenkins as a service, but instead of having any
build script launching SE server, we setup the build nodes to launch
SE server through the console command on startup on each node. That
means it will be running constantly on those nodes. We are using
Windows machines with a batch file kicking off the launch on startup,
but I'm sure the same can be done on a Linux based OS with a shell
script or cron job.
This may not be the best solution for everyone, but it's currently
working for us.
On Jun 4, 10:09 am, RonQ <
ronquin...@gmail.com> wrote:
> Did anyone ever provide a solution regarding this? I ran into the
> same issue. I too notice that you can only select "Allowserviceto
> interact with desktop" when you use a local user. Since we use a non-
> local user for our CM builds, I was not able to do this. I opted for
> the option of runningJenkinsthrough the console on the build node.
> I created a shortcut for it and put it in the Startup folder to ensure
> start-up on restart. That seems to work, but if anyone has a solution
> for getting the UI to work though theservicemethod I think that
> would be ideal.
>
> Best regards,
> Ron
>
> On Apr 17, 4:54 am, Daniel S <
danielstamm...@googlemail.com> wrote:
>
>
>
>
>
>
>
> > Thank you for your answer.
>
> > On the tomcatserviceGUI you can activate "Allowserviceto interact
> > with desktop" only with a local user, and in this case all works
> > fine.
> > But we need to use another User for theservice, and then its
> > impossible to check the checkbox. Is there a workaround?
>
> > Kind regards
> > Daniel
>
> > On Apr 13, 10:07 pm, Fernando Cervera <
fernandogcerv...@gmail.com>
> > wrote:
>
> > > In case that you are runningJenkinsas a windowsservice, you should
> > > either activate the checkbox "Allowserviceto interact with desktop" on
> > > theservice, or just run it from the console with "java -jarjenkins.war".
> > > The later option is what i'm using at this moment.
>
> > > Hope it helps.
>
> > > On Thursday, April 12, 2012 1:09:28 PM UTC-3, Daniel S wrote:
>
> > > > Hello,
>
> > > > we implemented a testautomation and it works locally very good, but we
> > > > want it run on our Server, too.
> > > > So we created ajenkinsbuild for the testautomation and we got
> > > > following error:
>
> > > > Could not start Selenium session: Failed to start new browser session:
> > > > Error while launching browser
>
> > > > Is it possible,that there are problems because it runs in a tomcat
> > > >serviceand so it doesn't have it's own "graphical interface"?