That's what I thought also, so I tried on my own Jenkins but it didn't work :-(
Maurice -----Message d'origine----- De : Mark Kessler [mailto:kesslerconsult...@gmail.com] Envoyé : mercredi 11 décembre 2013 10:48 À : Dev@Flex Objet : Re: [Builds/Jenkins] Help and advise needed Could try adding a basic user account and making the service use that instead. User accounts should be able to access the gpu. -Mark On Wed, Dec 11, 2013 at 2:45 AM, Maurice Amsellem < maurice.amsel...@systar.com> wrote: > >To avoid the window > Thank you for the suggestion, but I don't think the window is an issue. > It's rather that when running as a service (System or use account), > Jenkins slave cannot access the gpu / openGL. > > Maurice > > -----Message d'origine----- > De : Peter Ginneberge [mailto:p.ginnebe...@gmail.com] Envoyé : > mercredi 11 décembre 2013 04:02 À : dev@flex.apache.org Objet : Re: > [Builds/Jenkins] Help and advise needed > > To avoid the window, run the service under a different user, e.g. > "System" instead of a specific user or vice versa. > > Peter > > On 10/12/2013 22:55, Maurice Amsellem wrote: > > According to jenkins gui, there are 4 ways of starting the slave : > > - Java web start (JNLP) > > - command line from master > > - via SSH on Unix machines > > - as a Windows Service. > > > > I am using JNLP, but maybe the other launch methods don't get a window. > > I am going to try "as a Windows Service". > > > > Is there a way to know how the slave is launched on b.a.o? > > > > Maurice >
