What happened to CI / Jenkins?

Discussion in 'Bukkit News' started by EvilSeph, Jan 21, 2012.

Thread Status:
Not open for further replies.
  1. Offline



    Three days ago we were forced to lock down our build server, ci.bukkit.org, due to high load from all of you eagerly smashing F5 to see if a new Recommended Build had come out. While it is awesome that we have such a following that this is even possible, unfortunately CI runs on the same box as the rest of our sites and took down our site and forums whenever CI was under heavy load.

    As a result, I had to make the difficult decision of stopping all public access to our build service in order to restore stability and reliability to our website and forums. Once we had done this and the site was mostly reachable and usable, we immediately went on a hunt to determine what the cause of the poor performance was on our servers. Although the site is relatively stable, we're still seeing problems crop up now and again and are doing whatever we can to get down to the bottom of things. As part of this effort, we'll be experiencing minimal downtime on Monday as we'll be updating various aspects of our main server and it will require a reboot. After doing so, we'll continue to monitor the situation and see what we can do to continue to improve things.

    So what are we doing to solve these issues? We're actively working on developing a better way for the community to find and acquire our builds and releases and hope to have a suitable solution ready within the next few days.

    While we fully intend to continue to utilise Jenkins to provide us with continuous integration and reactive build compiling, we feel that Jenkins isn't a suitable solution for providing a user-friendly download experience for our community. As a result, we've been working on an easy-to use solution better designed to meet the needs of both our developers and our server admins. By combining the invaluable information usually provided by Jenkins (build numbers, changes and associated commits between builds, and so on) with a better user experience and intuitive design, we'll be able to provide an optimised, well cached site that can withstand the level of traffic we see day to day while still providing the community with up-to-date information about the latest builds and more.

    Thanks for your patience and understanding while we investigate the cause of the issues we've been having and make changes to address them, your continued unwavering support means the world to us.
  2. All hail Jenkins!

    No, I kid. I use the RSS, and CraftBukkitUpToDate. But from what I've seen, you folks seem to be concerned about the level of user-friendliness in Jenkins, right? It's no more unfriendly than the server itself, it only took me 40 seconds to learn how to be given a full list of all the Recommended Builds by promotion status. Interface isn't something I'd be concerned about. Ever.
  3. Offline


    That is actually a true story.

  4. Or you could remember why not every single build they bash out is a "recommended build", like Chikyuno (sadly, too late). Whenever you download a development build (so called because it is not fully developed yet), you enter into an agreement that you accept all liability for damages caused to your server and world by malfunctions from the plugin. They never promoted those builds as stable, or, y'know, recommended.
    That is why most smart people keep backups, especially when they tinker with things that are liable to break down.

    Development builds have not been beta-tested or stress-tested against any advanced mode of failure, and not once do people promote it as safe for use - that's what Recommended Builds are for.

    Don't blame the plugins for a lack of foresight on your collective behalfs. It's your faults you tried to use a plugin you knew could break at any moment without taking preventative steps in the likely event that it did screw up.

    A thirty-second MSPaint rendition of the no-stone snafu. Stop whining. (open)
  5. Offline


    Your own reply goes a long way to prove that you should keep Jenkins public, as there is already infrastructure in place that depends on it being there. This on top of my previous post leads me to the same conclusion as before, don't try to reinvent the wheel.

    ^^^ This is one of the most valid points I have seen in this thread, if you cant figure out the server itself you have no business poking around in Jenkins

    Nox13last likes this.
  6. Offline


    I'm sorry you spent so much time on that. I had a backup of my worlds and luckily we noticed the problem right away (and fixed it). Maybe you'll get some mileage out of that rant from the other guy though. Later, gator :p
    Nox13last likes this.
  7. I see what you did there.

    You, sir, are smart. One of the (if not the) smartest I've seen regarding this stone glitch. My rant is not lost on you, sir, but if only everyone had your precence of mind, there'd be no need for support.
  8. Offline


    Which is why you don't use Spout, that is a problem with Spout not CraftBukkit. This means that Spout has not updated their plugin to work with the latest API changes/etc, so of course most plugins will not work.
  9. And which is why they announce when they do update.They announce when they've got a build they've hammered at furiously without it screwing up.

    Does anyone here actually know the definition of "recommended"?
    Wulfspider, Darky1126 and NuclearW like this.
  10. Offline


    Though this may seem like a good idea disabling it would only make everyone manually refresh the entire page instead of the one feed. Which would actually tax the server more than it did before in case that wasn't clear.

    Gotta love dictionary.com

    "to present as worthy of confidence, acceptance, use, etc.;commend; mention favorably:"
    Nox13last likes this.
  11. And it's a shame that the only person who thought to answer that utterly non-rhetoric question used a dictionary. Although yes, credit. It means to present as worthy of confidence. Which, in all of the cases presented, the respective developers did not.

    About 70% of the people involved in this topic complain when they download a development PROTOTYPE build. They're absolutely dumbfounded when something goes wrong. That, somehow, pressing the link to download is intrinsically a guarantee that the product will work like a dream and make all of your projects awesome and fart diamonds out of your CD Drive, and all the rest.
    That only the "failed" builds with the red light next to them have the problems, and there's no difference between a build with a star next to it and one with a blue light next to it.
    Developers builds are only supposed to be used in special circumstances, circumstances where it may be necessary to use an experimental feature or take a risk.

    And if you can't tell the difference between one build and the other, then put your server down and go back to ROBLOX. We don't need you.

    And to say nothing of people who put a prototype CraftBukkit and a prototype Spout together. What the hell are you people thinking?!
  12. Offline


    The only reason I did that is because I wanted an exact definition I'm a perfectionist most of the time.

    Also to add to what you said the failed builds most likely means that there was a syntax or logic error which is different from a bug.

    An error is something that is fundamentally wrong whereas a bug or glitch is an unexpected side affect of how it was coded. (incase anyone didn't know there are many ways to do any one thing in code)
    Nox13last likes this.
  13. Offline

    Deleted user

    I'm thinking that you and other people are starting to turn this post into a debate.
    Mind locking this up?
  14. Offline


    Given that this thread as served it's purpose and is now starting to turn into a debate about various other matters, I am locking it.
    dark_hunter likes this.
Thread Status:
Not open for further replies.

Share This Page