Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Do Any Development Shops Build-Test-Deploy On A Cloud Service?

Posted by Unknown on from the raining-dev-builds dept.

bellwould (11363) writes "Our CTO has asked us to move our entire dev/test platform off of shared, off-site, hardware onto Amazon, Savvis or the like. Because we don't know enough about this, we're nervous about the costs like CPU: Jenkins tasks checks-out 1M lines of source, then builds, tests and test-deploys 23 product modules 24/7; as well, several Glassfish and Tomcat instances run integration and UI tests 24/7. Disk: large databases instances packed with test and simulation data. Of course, it's all backed up too. So before we start an in-depth review of what's available, what experiences are dev shops having doing stuff like this in the cloud?"

6 of 119 comments (clear)

  1. 50%+ cheaper not to use the cloud by Anonymous Coward · · Score: 2, Insightful

    It is 50%+ cheaper if you use in-house hardware. This assumes that you are a trained system administrator and you purchase energy and cost efficient hardware. Also, your data will be yours and not Amazons.

  2. EC2 likely too expensive.. by BenEvans7166 · · Score: 2, Insightful

    If it's all Java / JVM, then look at the Cloudbees offering, or the Waratek JVM (high-density) on something cheaper than EC2. Unless you have a decent grasp of when your environment can be shut down, EC2 is almost certain to be a waste of money, especially for dev / test.

    1. Re:EC2 likely too expensive.. by Slashdot+Parent · · Score: 3, Insightful

      EC2 likely too expensive.. [...] If it's all Java / JVM, then look at the Cloudbees offering

      You do realize that Cloudbees runs in EC2, right?

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
  3. Security concerns by Anonymous Coward · · Score: 3, Insightful

    If the stuff (data, processes, etc.) you put in the cloud are in any way sensitive, I would be very hesitant to put that in the hands of another company because of privacy and security. Particularly depending on your terms of service agreements with your users. I would avoid putting your source control system in the cloud too because then it's more accessible by nefarious actors than if it's locked down internally. This is of course assuming you have good security standards and practices in place.

  4. Re:We do by Lumpy · · Score: 5, Insightful

    "cloud makes it not matter where you're working from."

    Competent IT and VPN does that as well.

    --
    Do not look at laser with remaining good eye.
  5. How is it different? by msobkow · · Score: 4, Insightful

    When working for companies, everything was "in the cloud" already: on remote servers. It's not like I was running the stuff on my desktop.

    SSH to Amazon or SSH to a box in the closet. Pretty much no difference to me.

    --
    I do not fail; I succeed at finding out what does not work.