• 18
    And git too probably because the commit message is shit and the commits are probably not necessary
  • 2
    @Codex404 the commits are indeed necessary, cause we use aws codepipeline, so the only way for me to test something is to commit it and push it to the repository =/
  • 2
    Git interactive rebase?
  • 5
    @ArchanjoJr wait wut, no local testing?
  • 16
    Are you seriously not testing this query in a local db before pushing to aws?

    Talk about testing in prod 😟
  • 10
    Open heart surgery
  • 2
    I can relate to this a little, testing the pipeline that fails in Bitbucket but works locally.
  • 3
    Update query

    Update query new

    Update query new new

    Update query final

    Update query final most
  • 1
    @ArchanjoJr Well just put them into a branch and squash them at merge.
  • 6
    @iamavalos i work in 3 environments

    Local, staging and production
    Staging and production are both in AWS.

    No query is ran directly against production without first giving expected results in the first two environments. EVER!

    Yes it’s hard to get the data you need across all dbs, but then the local and staging dbs aren’t hard to generate semi valid data for, or if you must... do a mysql dump from production and load it up locally to test against.

    As for prod only environments, I do have a handful of projects that come under that, which I jump in and create temp tables of existing data and test against that, then delete the temp tables execute the queries against the real ones when satisfied it works.

    There’s always a way to test things.
  • 1
    @ArchanjoJr know your paine
Your Job Suck?
Get a Better Job
Add Comment