TFS & GO & Chef, oh my: Onboarding update!

Well, as of yesterday afternoon, we have one website and one database actively onboarded into our automation system.  Unbelieveable amount of work, but totally worth it.

What was chosen as the candidate for this pilot is our primary web front-end (referred to as WebUI here on out) and (one of) it's accompanying databases ('the database').  I'll try and describe what we're doing and how it's getting accomplished.

Pipeline overview of today, anyways...
  • Database (pipeline group)
    • Database Build (pipeline)
      • Builds the SQL scripts - we have pre/deploy/post scripts - pre/post are data transformation, 'deploy' is functionality-related.  Dev opted to use the VS equivalent of SQL compare - we will be using the Prod database as the true reference.  The 'deploy' scripts are automatically generated - pre/post scripts are done by hand and are optional.
    • Database Deploy (pipeline)
      • Snapshot script - 'reverts' the snapshot, takes another snapshot - after the sprint is over we 'commit' the snapshot data (I am not used to SQL snapshot terminology, sorry), so when the next sprint starts there is no snapshot present - all deployments during the sprint effectively 'start at the beginning' - hence QA injection in smoketest....
      • Execute SQL scripts in order - we are using the SQLPS module to do all our SQL commands/executions - I will do another post on that
  • WebUI (pipeline group)
    • WebUI Build (pipeline)
      • Builds from a VS setup project
      • Moves files/configs around
      • Imports the build output as a Go build artifact
    • WebUI Deploy (pipeline)
      • DeployFiles
        • Fetches the Go build artifact
        • Zips the files, sends to server(s), sends environment-appropriate configuration files
      • Chef run
        • Runs 'chef-client' on target server(s) - just a website restart/appPool recycle right now
      • Smoketest
        • Dev coded up an Nunit/Selenium test that does two things:
          • Ensures basic functionality is present (login, adding users, etc)
          • Injects 'QA data' into the database via the functionality test

Lessons learned

  • There is always a struggle between doing it right and doing it on time, and having people on the team who are on both sides can be a benefit.  
    • All on one side tends to either not get anything done or not get anything done well.
    • Caveat being that you must understand 'what's fundamental to get right from the start?' and be able to live with non-fundamental garbage for a time.
      • Parameterizing your scripts is fundamental (i.e. building blocks)
      • Having the scripts execute in 30s vs. 2m is not fundamental (i.e. performance improvements)
  • If you find yourself with a huge might be doing it wrong.
    • We were bashing our heads trying to figure out how to do the whole 'build repository' thing...ya, there's something called a build artifact that Go 100% manages for you.
    • We had initially been 'pro-Git' because the internet said so.  We are now 100% TFS (ok, except for Chef) because it just wouldn't work trying to mash both together.
  • Keep up the enthusiasm!  Eventually it'll catch on.
    • Keep up the momentum and people will get caught Katamari Damacy

Next steps

  • We have the remainder of the sprint to really see how this is to live with...and to move into the other environments (past QA), but everybody is pretty excited.  They've already come up with another project to onboard - this one right from Day1!
  • Communication of these changes to the rest of the team is also big - this is a totally new way of thinking, so we need to ensure everyone is aware of the benefits/changes to process.
  • A lot of cleanup to do with our deployment scripts, pipeline config (some jobs still called 'DefaultJob') - but it's just polishing/templating for the most part - at least right now.  We also still have to onboard the UAT/Prod environments.
  • For funzies we put together a Selenium Grid system...annnd now it's a thing.  Dev is working on getting Appium integrated.  We have two nodes for web browsers already.
  • Also...we have an automation person starting on Monday - should be pretty exciting to see where that goes.  

Hectic times ahead, but super exciting!  Things are going to be mega-hyperbole-busy for the next few months...colo move...automation...two production environment moves...more automation...monitoring...


Popular posts from this blog

Learning through failure - a keyboard creation journey

Learning Opportunities - Watching/listening list

DFSR - eventid 4312 - replication just won't work