Just figured this out. My application had moved onto Play 1.2.4 whereas Jenkins was using Play 1.2.3! I feel a bit sheepish that I hadn't noticed this earlier, but I also wish that the console had printed out a more helpful error than IOException.
Will On Feb 4, 2:53 pm, Sami Tikka <sjti...@gmail.com> wrote: > Could it be that you are running Jenkins on a Mac? > > Have you recently updated Jenkins? > > Did you perhaps choose to run Jenkins as user "jenkins" instead of > "daemon" like you used to? Maybe you have something in your build that > depends on being run as "daemon"? Or did you set some customized > setting in /Library/LaunchDaemons/org-jenkinsci.plist file and it got > overwritten by the Jenkins upgrade? > > If the former, I'm sorry but I'm not familiar with the play framework > or how you have installed it. > > If the latter, you can make a customized installation and choose to > either "Start at boot as daemon" or "Start at boot as jenkins". If you > do choose neither, the org.jenkinsci.plist file will not be > overwritten and you are free to change it how you want. > > The customized installation can be invoked with the button titled > "Customize" in the Apple Installer. (I thought I should mention it > because I have recently learned not many people are aware of that.) > > -- Sami > > 2012/2/1 Will Chan <w...@egraphs.com>: > > > > > > > > > I have Jenkins testing my Play Framework application. It ran just fine > > until a recent checkin. I am trying to debug why Jenkins stopped being > > able to start the application, but I could use some advice. > > > My commands are: > > play clean # cleans the tmp files > > play deps # downloads maven dependencies > > play auto-test --deps -Djava.awt.headless=true -Xmx2048m > > > Here is what the console output looks like now: > > > ... downloads dependencies ... > > ~ Done! > > ~ > > ~ The application does not start. There are errors: > > java.io.IOException: Server returned HTTP response code: 500 for URL: > > http://localhost:90...@tests.list > > ~ _ _ > > ~ _ __ | | __ _ _ _| | > > ~ | '_ \| |/ _' | || |_| > > ~ | __/|_|\____|\__ (_) > > ~ |_| |__/ > > ~ > > ~ play! 1.2.3,http://www.playframework.org > > ~ framework ID is test > > ~ > > ~ Running in test mode > > ~ Ctrl+C to stop > > ~ > > ~ Deleting /Users/Shared/Jenkins/Home/jobs/eGraphsServers/workspace/ > > tmp > > ~ > > Listening for transport dt_socket at address: 8000 > > 00:14:34,509 INFO ~ Starting /Users/Shared/Jenkins/Home/jobs/ > > eGraphsServers/workspace > > 00:14:34,512 INFO ~ Module cloudbees is available (/Users/Shared/ > > Jenkins/Home/jobs/eGraphsServers/workspace/modules/cloudbees-0.2.2) > > 00:14:34,512 INFO ~ Module less is available (/Users/Shared/Jenkins/ > > Home/jobs/eGraphsServers/workspace/modules/less-0.3.compatibility) > > 00:14:34,513 INFO ~ Module scala is available (/Users/willchan83/lib/ > > play-1.2.3/modules/scala-0.9.1) > > 00:14:35,839 INFO ~ Scala support is active > > 00:14:35,889 WARN ~ Using implementation version: Rhino 1.6 release 7 > > 2011 09 02 > > 00:14:36,183 WARN ~ You're running Play! in DEV mode > > ~ > > ~ Go tohttp://localhost:9000/@teststo run the tests > > ~ > > 00:14:36,252 INFO ~ Listening for HTTP on port 9000 (Waiting a first > > request to start) ... > > ~ > > ~ > > Executing /Users/willchan83/lib/play-1.2.3/play javadoc "/Users/Shared/ > > Jenkins/Home/jobs/eGraphsServers/workspace" > > [workspace] $ /Users/willchan83/lib/play-1.2.3/play javadoc /Users/ > > Shared/Jenkins/Home/jobs/eGraphsServers/workspace > > ... > > > So.... the question is why does the application not start. I tried > > increasing the heap size for these tests, but this still happens. Does > > the exception suggest anything to anyone? Are there logs I should look > > at? > > > Thanks in advance for any forthcoming advice! > > > Will
