everything on the same host for now. but the build farm is coming
eventually.
On Mar 7, 3:36 pm, Les Mikesell wrote:
> On Wed, Mar 7, 2012 at 8:20 AM, jabal wrote:
> > the solution was that Selenium tests made firefox-bin crash because
> > the $HOME variable was not set.
> >
the solution was that Selenium tests made firefox-bin crash because
the $HOME variable was not set.
This pulled Jenkins down and when the service manager saw it then
restarted Jenkins service.
On Mar 7, 9:02 am, jabal wrote:
> (1) I moved running these tests to a separate jenkins job but
Further investigations showed that 'firefox-bin' crashes and that
takes the Jenkins JVM down and the service manager restarts it.
On Mar 7, 9:02 am, jabal wrote:
> (1) I moved running these tests to a separate jenkins job but it still
> restarts.
> (2) I placed the ant invocat
Further investigations showed that 'firefox-bin' crashes and that
takes the Jenkins JVM down and the service manager restarts it.
On Mar 7, 9:02 am, jabal wrote:
> (1) I moved running these tests to a separate jenkins job but it still
> restarts.
> (2) I placed the ant invocat
(1) I moved running these tests to a separate jenkins job but it still
restarts.
(2) I placed the ant invocation into a separate shell script and the
my single build step is
executing this shell script: jenkins still restarts.
very strange..
On Mar 7, 8:45 am, jabal wrote:
> hi!
>
>
hi!
I'm quite new to Jenkins CI but happy to have assembled a freestyle
project that builds and test my program starting from git checkout. As
the final point I wanted to integrate my Selenium tests into this
process and added a final Ant build step that calls this target. I was
struggling with th
