There has been a lot of cool stuff mentioned on NSBCon so far.
But how do make sure you actually get to use it.
Ie avoiding =>
Show of hand, who’s on v2.X?
V2.X migrate to v3.3.8 you’re covered from then on
3.3.0 was released Monday, October 29 2012 =>2 y
This talk is about what we do now and plan to do in order to help you keep updated while keeping the risk low
Its not only the big and cool features you heard of so far
We’re upping our game in terms of CD
“Reliable software releases through Build, Test and Deployment Automation”
Provide value faster
Will also give feedback faster
Provide hotfixes, god forbid, more timely
2014, 41 so far => on target for 80 + this year as well
We are releasing more , 2 release per week on average
Monthly cadence for minor releases
This is all fine and dandy but it might inflict…
We don’t want our release schedule to cause customers falling to far behind
Warstory - Swedish government agencies
The consultants are now long gone, so is the CD-disk where they put the source code
Leads to big bang upgrades
Big bang releases are risky
And risk equals cost
But lego is cool, this is the big bang we want to avoid
Big Bang (Korean: 빅뱅; often stylized as BIGBANG) is a South Korean boy band formed by YG Entertainment. Leader G-Dragon, T.O.P, Taeyang, Daesung, and Seungri officially debuted as a five-member group on August 19, 2006.
After listening to their music, this is the big bang you want to avoid
Big risk
The risk is compounded
Leads to a Coorporate decision
Force CXO signoff
Drives costs
Solution: Upgrading one endpoint at a time
Needed since we push users to build systems made of many autonomous endpoints
Allows for updating endpoint by endpoint leading to mixed environments =>
Allows you to evolve at your own pace
New projects should default to latest NSB
This is what you have to do:
Message contacts , they should use unobtrusive
We tackle it with TC + AWS + Azure
Significant cost
But we couldn’t afford it without the cloud
This has been a long journey during the last few years, this is what we’ve learned
War story on how we released in 2011
Refer back to Ud’s statement about the Download now button
Things are different now, nuget, chocolatey, visual studio gallery etc
Automate all the things
To make sure quality isn’t degrading
To not rely on humans remembering
To avoid depending on individuals
How to get there
Document the steps
That is your list of potential automation
Choose the best tool for the job: github , tc, trello, hipchat, hubot
Use tools that can be composed and extended
But sometimes there is no tool
How gitversion has lead us to focus more on if it’s a hotfix or not and care less about version numbers
GV assigns a SEMVER according to the git repo
Needed since we have so many repos now
Has lead us to focus more on if it’s a hotfix or not and care less about version numbers
The netscape (back in the days) core value
Holds true today