Thank you so much for your kind help! Jenkins 1.500 is running on Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86. Configured inside is JDK 1.6.0_38 and JDK 1.7.0_11, and Maven 3.0.4. I downloaded the latest and greatest WAR and put into /var/lib/tomcat6/webapps as ROOT.war (so it is the only bound WAR). Added plugins: * Jenkins GIT Plugin 1.1.26 * Jenkins Cobertura Plugin 1.8 * Config File Provider Plugin 2.4 (added more since the weird problem occurs, so they do not play a role) The last actions I did before the system gone wild: * Copied a native job that was working properly before. The job itself is simple, it just checks SVN and calls ANT, nothing special. * Executed that job. (in fact I had a similar problem before in another Jenkins domain where copying a native job also produced "weird" problems). Jenkins itself and the OS had not been touched in any way. It just started after the copy was done. I will look up the other information you asked for and post it ASAP. Thanks so far Markus
Am Samstag, 9. Februar 2013 19:56:21 UTC+1 schrieb sti: > Sorry, but ... Have you tried turning it off and on again? :) > > And check the stdout and stderr of Jenkins. Is it printing exceptions > and/or stacktraces? If so, put them into pastebin/gist and tell us. Also it > might be helpful to see your config.xml files (and remember to remove any > sensitive information from those before publishing). > > Also, give us information just like you would if you were talking to an IT > support person: > > - What is the operating system on which you are running Jenkins? > > - How did you install Jenkins? Used one of the platform-specific > installers or rolled your own? > > - Running inside a servlet container? > > - Plugins and their versions? > > - What did you do recently? Did you upgrade Jenkins? Or upgrade one or > more plugins? Or upgrade something in the operating system? > > - Pastebin/gist where Jenkins stdout+stderr can be found. > > -- Sami > > Markus KARG <mar...@headcrashing.eu <javascript:>> kirjoitti 9.2.2013 > kello 20.29: > > > One more "nice" thing detected now... Clicked on "build now", build > finished successfully, then clicked on the build number to see the result, > got "404 NOT FOUND"! > > > > Am Samstag, 9. Februar 2013 19:28:21 UTC+1 schrieb Markus KARG: > > Til today my Jenkins 1.500 worked well. > > Then I started setting up a Windows slave, and added a few free style > ant projects running on that slave. > > It all was good, but since I copied one of that free style projects, my > dashboard is running crazy. > > It misses builds that just finished a minute ago. > > It shows builds starting without any reason. > > The total horror it showed one minute ago: I clicked on the "start > build" button on project X and INSTEAD it started project Y. Both have > different types and are totally independend. But when the build was gone, > all builds were gone. > > And so on. Just like a total crazy Jenkins that didn't take his pills in > the morning. > > > > Please help, I don't know how to bring him back to reason! > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to jenkinsci-use...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
