We get things so ass-backwards. How do we get code from development team to the end user? I’ve written an article on this subject at InfoQ. I hope you like it.
-
Urbancode's DevOps Platform provides end-to-end build and
deployment automation.. Blogroll
Popular posts
Useful links
Meta
Categories
- .NET (7)
- Build (51)
- Comics (4)
- Conferences (15)
- Continuous Integration (110)
- Deployment (13)
- DevOps (3)
- eXtreme Feedback Devices (16)
- Java (15)
- Jobs (8)
- News (156)
- links (125)
- Opinion (5)
- Patterns and Practices (23)
- Ruby (7)
- Site Admin (10)
- Systems Administration (11)
- Tools (5)
- Uncategorized (25)
- Version Control Systems (7)
- Video (7)
Job Board Menu
-
Home
Jobs
-
Test Job Post
at Test Job Post
Location: Test, United Kingdom -
Integration/Configuration Engineer
at Eloqua
Location: Vienna "Tyson's Corners", VA -
System Administrator / Devops
at Opera Software
Location: Melbourne, VIC, Australia -
Devops / Sysadmin
at onefinestay
Location: London, United Kingdom -
Devops Engineer / Build
at Gemvara
Location: Boston, MA
-
Test Job Post
at Test Job Post
2 Comments
Nice piece. There’s a reason why companies, and even volunteer projects, don’t instinctively want to release very frequently: experience teaches us that releases introduce bugs. The key to overcoming this resistance to frequent releases is (IMHO) comprehensive functional and non-functional testing. As all the non-developer types involved with a release gain confidence in the release process as solid, so the frequency of releases can be accelerated.
I’m not a developer, so it’s easy for me to say, but the better the dev team I’ve worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down….
Gary, thanks for the comment. I wouldn’t shoot you down. The moment a dev team thinks that testing is someone else’s problem, the rot sets in. Or the build, for that matter.
Post a Comment