• Noughmad (unregistered)

    Automatic first post!

  • Second (unregistered)

    Second

  • James Chorlton (google)

    This sounds very much like something someone I know would do..... No names because job and all that.

  • GordonFreemanK (unregistered)

    To be fair it sounds like the deployment process should be the same in UAT and prod. Lars' "automatic" deployment procedure has not been UAT'd so it's not only Lars' fault if it failed... There's something broken higher up in their release process.

  • MoSlo (unregistered)

    Deployment to live environment different from UAT environment D:

    One of the first questions I ask over a new project is how it's going to be deployed.

  • David (unregistered)
    The development and testing process had been rigorous, but Brody felt confident in his code after receiving UAT signoff the week before. There was even time for extensive load and stress testing this time around. Brody spent most of the weekend running builds and packaging up the code and database scripts so that Lars and Co. could prep the deployment first thing Monday.

    Why was Brody building and packaging the code in the weekend, while UAT already signed off on the code the week before?

  • Nicholas "LB" Braden (github)

    I was afraid the automatic deployment worked by sending every file via email to the server...

  • oscar carserud (unregistered)

    I couldn't deploy yesterday,because I was a robot. Testing g today. Hi world.

  • Quite (unregistered)

    QFT.

    So a year ago I was investigating the build process of the project for which I was increasing my responsibility. "It's all automated," said the build owner, "no worries."

    "Sorry," I said, "but I do worry, can you send me a copy of the build script? I need to make sure it's appropriately generic, so we can use the same script for all our products in this line."

    "Oh no, it cannot be made generic," said the build owner. "The project name is hardwired into it."

    "And it can't be changed why?"

    "You can't change the build script," said the build owner. "That would be wrong."

    "Can you pass me the build script anyway? I need to review it." And I waved my new job title at him, which included within its implicit specification: "I am superior in authority to the build owner."

    "Can you set up a meeting online for tomorrow afternoon, then?" he said, "Two hours should be enough."

    Yes indeed, two hours was just about enough for the full enormity of the "automatic" build process to be demonstrated to me, and 7 or 8 pages of A4 handwritten notes just about covered everything. Most of this was not even written down, but stored in his head: "Oh yes, and don't forget to go into such-and-such a folder and copy this-and-that file into hence-and-so ..."

    After another week's work I had completely automated the build (just an ant script with a bat front end to run it via). Then a directive came down from Heaven above that everything was to be built from now on using Maven. With a sigh of relief and the sense of disinfecting my hands after having cleaned a toilet, I passed the whole damn lot to the Maven automatic overnight continuous integration team.

  • Nagesh (nodebb)

    Pretty standard practice of making change to configuration before deployment to production

  • Phil Longenecker (google)

    Great, another site that grabs my personal info from google and won't let go. Nice job, you selling this to the spammers that have been hitting me hard the past week?

  • CoyneTheDup (nodebb)

    It would have been fool-proof...if they had left out the fool-manual-handling.

  • dumbasstwopointomg (unregistered)

    so it was a mistake, but you'll correct me if i'm wrong: wasn't (a) the implementation successful and (b) didn't it take significantly less time than the previous one?

  • Doh! (unregistered) in reply to CoyneTheDup

    Dear Mr. Phil Longenecker -

    Why did you feel you had to sign in with google? You could have used GitHub, Facebook, or a NodeBB account from the forums here! Heck, there's even the option to post anonymously, as I have just done.

    Sincerely, Homer Simpson

  • spezialpfusch (nodebb)

    As automated as everything is in that place, I am sure they have no automated uninstallation for Lars from his current job position. ;-)

  • Bananafish (nodebb) in reply to dumbasstwopointomg

    Yes, it does seem that way. But I think the point here is the "new-and-improved" version of the "automated-deployment-tool" is as chock full of WTFery as the old-fashioned manual way.

    Some things don't automate well. This is not one of those things.

  • PWolff (nodebb)

    Fully automated disployment. Just the usual stuff.

  • Kempeth (unregistered)

    This configuration file was sent by my new Samsung Galaxy S6!

  • Oli C (unregistered)

    "...spent most of the weekend running builds and packaging up the code and database scripts so that Lars and Co. could prep the deployment first thing Monday. "

    Stop. Right. There.

    Surely the code and DB scripts had been packaged already when building the UAT system which is a mirror of the Live environment?

    If your deployment isn't tested and isn't packaged and repeatable, you're going to have a bad time.

    And if you're "running builds" after UAT, you just (potentially) nullified the UAT. You are now releasing code to live which is different to that which passed UAT.

  • Joseph Osako (google) in reply to Quite

    Yes indeed, two hours was just about enough for the full enormity of the "automatic" build process to be demonstrated to me, and 7 or 8 pages of A4 handwritten notes just about covered everything. Most of this was not even written down, but stored in his head: "Oh yes, and don't forget to go into such-and-such a folder and copy this-and-that file into hence-and-so ..."

    I was going to point out that you had used the wrong word, but reading the rest of this, I agree that 'enormity' is indeed the appropriate description.

    e•nor•mi•ty (ĭ-nôrˈmĭ-tē)►

    n. The quality of passing all moral bounds; excessive wickedness or outrageousness. n. A monstrous offense or evil; an outrage. n. Great size; immensity: "Beyond that, [Russia's] sheer enormity offered a defense against invaders that no European nation enjoyed” ( W. Bruce Lincoln).

    Oh, it works either way, given the third definition, but the first two fit this case better IMAO.

  • Randal L. Schwartz (github)

    "Brody resisted the urging of his buddies to hit the bar earlier so he could be clear-headed for the release."

    So hitting the bar earlier would have made him clear-headed for the release? I think that sentence is a bit too complex.

  • kangroo (unregistered)

    I have been in the industry for close to 10 years now, and I have never seen a place where UAT environment is same as Live. so testing deployment scripts in UAT is not going to help absolutely.

Leave a comment on “A Signed Release”

Log In or post as a guest

Replying to comment #:

« Return to Article