TIBant™ v2 has just been released and for us, it’s very special. It’s not special because of any particular new feature within TIBant itself; it’s special because of how it has been released.
For a while now (see item 4) we’ve been students and advocates of continuous delivery and its sometimes scary cousin, continuous deployment, and it’s about time we started taking our own advice for our current projects. This is exactly what we have done with TIBant. TIBant was released using a continuous deployment approach, with commits to the code repository triggering a series of dependant Jenkins Jobs that run automated tests, create the TIBant zip files, publish them to an Ivy repository, upload them to Assembla and then post a notice on our website. All of it is automated; it’s been quite an experience. Continue reading What’s So Special About TIBant™ v2