AFAIK, you can as long as you enable the interactive services: http://stackoverflow.com/a/19947566 might help
Cheers On Thursday, 24 September 2015 10:21:23 UTC+2, Rohan Majumdar wrote: > > So, i guess there is no way to run the service as is and be able to see > the automation. > > Anyways my problem is solved. > I am using the JNLP agent manually. > Not as a service. > > Regards and thanks > Abbas > > On Tue, Sep 22, 2015 at 7:00 PM, Victor Martinez <[email protected] > <javascript:>> wrote: > >> That's actually the expected behaviour since Windows services uses >> Display 0 >> - >> https://msdn.microsoft.com/en-us/library/windows/desktop/ms683502(v=vs.85).aspx >> >> Just seen there was already some answers about this feature in the >> stackoverflow >> - >> http://stackoverflow.com/questions/18906753/jenkins-windows-slave-service-does-not-interact-with-desktop >> >> >> >> On Tuesday, 22 September 2015 13:57:32 UTC+2, Rohan Majumdar wrote: >>> >>> I have observed something weird, that the automation is visible when the >>> agent is not running as a windows service. >>> The automation visibility worked that way. >>> Discovered this by accident. >>> >>> On Tuesday, September 22, 2015 at 11:55:05 AM UTC+5:30, Victor Martinez >>> wrote: >>>> >>>> Let me ask you if you are launching your slave connection via windows >>>> services (point 6) or via JNLP connections (point 5) >>>> >>>> >>>> <https://wiki.jenkins-ci.org/download/attachments/41878276/setup03.png?version=1&modificationDate=1319630597000> >>>> >>>> JNLP shouldn't run in the background AFAIK. Have you tried to run those >>>> commands manually in the same windows box? Different behaviour? >>>> >>>> Cheers >>>> >>>> >>>> On Tuesday, 22 September 2015 07:18:53 UTC+2, Rohan Majumdar wrote: >>>>> >>>>> Yeah, I have followed the same tutorial while making the slave. >>>>> Once again testing works fine but the GUI automation is not visible. >>>>> I think it happens in the backfround. >>>>> >>>>> On Monday, September 21, 2015 at 6:09:37 PM UTC+5:30, Victor Martinez >>>>> wrote: >>>>>> >>>>>> See the below wiki: >>>>>> - >>>>>> https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines >>>>>> >>>>>> On Monday, 21 September 2015 12:41:04 UTC+2, Rohan Majumdar wrote: >>>>>>> >>>>>>> And yeah I am using windows Vista as a slave. >>>>>>> Windows 7 is the master >>>>>>> >>>>>>> On Monday, September 21, 2015 at 4:08:16 PM UTC+5:30, Rohan Majumdar >>>>>>> wrote: >>>>>>>> >>>>>>>> I have installed the java service on the slave, is that not JNLP. >>>>>>>> Can you please elaborate what do you mean by JNLP >>>>>>>> >>>>>>>> On Monday, September 21, 2015 at 12:36:06 PM UTC+5:30, Victor >>>>>>>> Martinez wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Are you using Windows slaves? If so, have you configured your >>>>>>>>> windows in order to support interactive sessions? IMO, I do prefer to >>>>>>>>> use >>>>>>>>> JNLP connections rather than Windows service connections since it >>>>>>>>> does >>>>>>>>> allow interactive sessions by default. Can you try to run your slave >>>>>>>>> as >>>>>>>>> jnlp connection? >>>>>>>>> >>>>>>>>> Cheers >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, 21 September 2015 08:58:20 UTC+2, Rohan Majumdar wrote: >>>>>>>>>> >>>>>>>>>> I have a jenkins slave to run the robotframework test cases. I am >>>>>>>>>> able to get the console prints on the master but no browser ever >>>>>>>>>> opens up >>>>>>>>>> or anything on the slave. >>>>>>>>>> Ofcourse the test case works pretty fine. >>>>>>>>>> But I am just curious. >>>>>>>>>> How to have the automated test cases play on the slave machine. >>>>>>>>>> There was post which says about running jenkins from the command >>>>>>>>>> line. >>>>>>>>>> But my confusion regarding that is -> Jenkins is configured on >>>>>>>>>> the master then how can we affect >>>>>>>>>> the slave by running jenkins on the console on the master please >>>>>>>>>> elaborate. >>>>>>>>>> There is no jenkins configuration other than the Java service on >>>>>>>>>> the slave machine. >>>>>>>>>> >>>>>>>>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/TCf_KhIgHVQ/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/ed126ad3-a644-474a-80d3-be3c51fcda29%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/ed126ad3-a644-474a-80d3-be3c51fcda29%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5ea24507-764c-48e2-9d00-3e5b6513559b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
