Unless you have changed the configuration by hand, the native OS X package sets up Jenkins as a launch daemon. Launch daemons have no access to window server, thus they are unable to display windows, like chrome.
You must run Jenkins as a launch agent or use https://github.com/stisti/jenkins-app -- Sami Liron Yahdav <[email protected]> kirjoitti 8.8.2012 kello 3.15: > I installed it using the Mac OS X native package link from the > http://jenkins-ci.org/ homepage. > > On Tuesday, August 7, 2012 2:01:02 PM UTC-7, sti wrote: > And how did you install Jenkins? > > -- Sami > > Liron Yahdav <[email protected]> kirjoitti 6.8.2012 kello 20.31: > > > TLDR: Running ruby scripts from Jenkins on OS X that use the > > selenium-webdriver gem with chromedriver causes the "Aw snap" page to come > > up in Chrome. Running those same scripts from outside of Jenkins works > > fine. Any ideas as to what's wrong? > > > > ------ > > > > Long version: > > We have a CI machine that's a MacBook Pro running OS X Mountain Lion with > > Jenkins installed. The Jenkins server runs as a user who can login to the > > system. We configured Jasmine to use Chrome for the `rake jasmine:ci` > > command by setting ENV['JASMINE_BROWSER'] = 'chrome'. This all works fine > > when running `rake jasmine:ci` from the command line on that machine, but > > when Jenkins is configured to run the same exact command, Chrome will start > > up and when it tries to hit the url to run the tests, the tab crashes with > > the "Aw Snap" error page. I looked at the chromedriver.log file that's > > generated and there are no errors, it basically just stops all of a sudden. > > The Jenkins build eventually gets a Selenium timeout error. > > I've tried setting up the same config on a MacBook Air running OS X Lion > > and the same problem occurs. > > We also have integration tests written with RSpec and Capybara and when we > > configure it to use Selenium with chromedriver, the same problem occurs > > when running through Jenkins, though the "Aw Snap" page comes up a few > > steps into the first test. > > > > Has anyone gotten a similar setup working or have any idea what the issue > > could be? Thanks! > > >
