Did you know it took Netflix eight years to modify their processes to do things the "DevOps way"? Even in significantly smaller organizations, making that cultural and technical transition is still a long process. Tool-wise, going down that path does not always mean using the newest and shiniest inventions. Sometimes, there will be intermediate steps and implementing them will be, well, not exciting.
It's important to take one step at a time and this talk is about that. I would like to present how Acrolinx – a company working heavily with computational linguistics – is changing its on-premise infrastructure, closing down old servers (Ubuntu 9.04 in 2016, anyone?), making work with Jenkins more friendly (while running close to seven hundred jobs on one Jenkins instance), juggling between Windows and Linux and re-discovering configuration management. It's a story of good decisions and mistakes that - hopefully - might reassure people that there is nothing wrong with taking things slow.
Vorkenntnisse
Understanding what Continuous Integration and configuration management are, basic Linux administration knowledge, basics of using Jenkins or other CI tools, idea about what DevOps is.
//
Marta Paciorkowska
@a_meba
is an activist/project manager turned infrastructure enthusiast. Marta currently holds the position of DevOps Heroine at Acrolinx, where she is responsible for developer support, redesigning build infrastructure and introducing DevOps ideas. She actively supports initiatives that make the tech community more inclusive. A *very* occasional Rails Girls coach. She ♥ Chef, alleycats and pizza.