Hey Martin, I think this was introduced by Adam in SIS-30 [1] when we put in Jetty integration in sis-webapp. I think Jetty is just picking the default port to run unit tests on (8080), and that port is in use from time to time. We should probably file a JIRA issue for this as a bug and simply update the config to choose a random, unused port.
Cheers, Chris On Sep 6, 2012, at 9:20 AM, Martin Desruisseaux wrote: > I just modified the Jenkins configuration as proposed in previous email, with > one additional change: I limited the builds saved by Jenkins to 7 last days > (previous configuration was putting no limit on the amount of builds to > save). Of course we can change that duration if we need a longer history. > > However we have random build failure. One of them is: > > Failed to execute goal (...snip...) (start-jetty) on project sis-webapp: > Failure. > Caused by: java.net.BindException: Address already in use > > I'm not familiar with Jetty, but I wonder if we are limited in the number of > applications using Jetty concurrently, in which case the build failure or > success would depend on the other projects being built concurrently. In such > case, one possible approach would be to disable the sis-webapp tests if some > profile in enabled, and that profile would be enabled on Jenkins. > > Martin > [1] https://issues.apache.org/jira/browse/SIS-30 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
