I'm interested in throwing together a "bukkit test server" that can be used to get the community more involved in the QA process and help the bukkit team get good metrics and coverage on new builds. The idea is that it would update daily to the very newest build, so that items could be well known and fixed. This is an agile methodology called dog-fooding that I have seen work well in other projects, as when a dev has to eat his own dog food, they typically do what they can to make it gourmet. I'm wondering what the community interest is from both the user and the development community, as I would need the support of both for this to work. Server is up: 69.42.218.43
I agree with this approach. I think creating an official "Test Server", along with its own "Test Thread" (where bug reports could be posted in an organized manner) would be most efficient. I am both a Bukkit community member and a newer plugin developer, and from both perspectives I would think this would help out the Bukkit Team immensely. The only problem is getting a dedicated server up and organizing what fashion we would use plugins to see what breaks what, and so on. I hope I've made some sense to you, because my idea itself seems pretty feasible.
Well I'm not sure how official I am, but I am interested in this.. and I have a server that currently not being used.
By "official" I mean that anyone can provide the server and then someone of higher authority can deem it "The Official Test Server of the Bukkit Project: For Testing Purposes Only". Proper advertising and organization, as well, will help the test server become "official" in the eyes of the community.
Good enough. I would suggest that mods and admins on this forum have the same access on the server. I'm updating the server now.. host is 69.42.218.43 well I would update, deploy this.. but the most recent version doesn't even run as a background process so suddenly none of te scripts that have always worked before dont work, and thus 95% of people wont be able to use it. EDIT by Moderator: merged posts, please use the edit button instead of double posting.
How would you go about plugins? Or do you only want to test vanilla bukkit for bugs like minecart + lava = crash? I wouldn't mind joining for a moment to do some crazy stuff and try to break the server
The idea would be this would be a "test server" so the more you can break it the better. Just having issues wit the builds atm, since somebody made a checkin that broke running it as a background process on centos and I keep getting exceptions about bad file handles when I try to use scripts that worked perfectly before. Code: >Mar 28, 2011 4:49:50 PM net.minecraft.server.ThreadCommandReader run SEVERE: null java.io.IOException: Bad file descriptor at java.io.FileInputStream.read(Native Method) at jline.Terminal.readCharacter(Terminal.java:99) at jline.UnixTerminal.readVirtualKey(UnixTerminal.java:128) at jline.ConsoleReader.readVirtualKey(ConsoleReader.java:1453) at jline.ConsoleReader.readBinding(ConsoleReader.java:654) at jline.ConsoleReader.readLine(ConsoleReader.java:494) at net.minecraft.server.ThreadCommandReader.run(ThreadCommandReader.java:25) 16:49:50 [INFO] Starting minecraft server version Beta 1.3 16:49:50 [INFO] Loading properties 16:49:50 [INFO] Starting Minecraft server on *:25565 16:49:50 [INFO] This server is running Craftbukkit version git-Bukkit-0.0.0-544-g6c6c30a-b556jnks (MC: 1.3)
I think there's a fine line between "doesn't work" and "can't run as a background process in Centos". The server is just trying to read from stdin, which it can't in this situation, and there's not graceful handling for that. Far from "doesn't work".
Dude, its a SERVER. Its designed to run as a background process. If it cant do that, it doesn't work. And on remotely hosted servers, this type of deployment is the most common way of doing it, so if its not supported and your forcing people to leave a putty/ssh window open to keep it running, thats fail. It worked before, now it doesn't. Thats a bug, and a functional feature that no longer works. Dont take it personally, thats not intended.
Oh right, he throws away input, well I personally use screen too, because you can easily get back to it. But file a bug anyway.
Server is up.. Yes, most people would rather not deal with the console, and screen is not an option for everybody.
I'm using the official builds as to do otherwise would sort of lesson the qa process since that is also what is being offered to peole, so compiling my own is not an option.