Time and cost saving Continuous Integration workflow for Drupal 8 teams.
Drupal 8 brings to us new level of maintainence effort in terms of development.
All previous skills almost non usable, like
- functional programming now is not effective, everyone needs to OOP
- skills means ability to understand somebody else's code
- creating new code means - reuse already providen by core and do not reinvent the wheel and do not throw new bugs.
- QA testing means more business logic oriented testing, instead of digging into the code.
- Micromanagement is not effective, should be automated from project start
- Automation means not making developer's life better, but saving money in terms of playing with competitors
- Contribution to Drupal.org means bringing team power to new level of public review for the team's activity
This session - is about success story of changing large Drupal development company to totally different way of teams communication, from Junior Developer to Team Lead or Administrative.
We've done a lot of improvements to our Continuous Integration, automated a lot of things, starting from developer's desktop, ending with Administrative team communication and Deployments automation.
Also, we are going to share how to bring CI maintainence as a product to a client. How to tell a client - you need automation, and why you need it.
So this session is going to be a success story of how to create a layer in your company, that helps all parts of the company communicate more effectively and get deadlines without breaking them.
We have 2 parts in our session.
- Technical one, about http://cibox.tools -> Continuous Integration suite
- Management part - about how to make CI as a major part in terms of a control over a team and work quality.