We are inspired by open source methodologies. We practice these within Endocode and help clients do the same.
Some time ago, when kicking off a new project to integrate yet another Jenkins based CI setup for one of our customers, they asked us for a rather unusual feature: a second Jenkins master the system can failover to in case of malfunction, that eventually would reduce risk of downtime. What we came up with, why we got there and how we implemented it is what we’re sharing here with you.
April 11 marks an important milestone in our favourite compliance project of the year: Quartermaster - the compliance tool that implements a full Open Sourcce license compliance audit as part of a modern DevOps cycle. On April 11, 2018 Endocode will host the Quartermaster v.0.2 requirement workshop. This workshop marks the end of the development of v.0.1 of Quartermaster. A development cycle that added a completely new architecture, a modular implementation, a master graph database, gPRC based APIs for phase-specific modules written in different programming languages, and more demo builds to the initial prototype.
“You build it, you run it” is not a philosophy that can easily be taken to non web tech industries. This harsh reality is something we ran into while making our journey through the automotive industry. But if we cannot duplicate this philosophy outside of our web tech bubble, maybe it’s possible to create a mentality that at least supports the feeling of responsibility for every line of code that eventually finds its way into a product.
Today is the 14th of February. An important day for people worldwide. Why? Well obviously because it is “I love Free Software”-Day! The “I love Free Software Day” is where we give a shout out and thank you to all contributors in the community. What unites us as a community is that we share ideals like collaboration, constant improvements and equal opportunity to access, learn and contribute to Free Software. And all this would not be possible without everyone contributing their piece of the puzzle: The developers, the designers, the translators, the lawyers, the testers, the documentation writers and last but not least, the pizza bakers.
Maybe it’s just me, but it seems like Marty McFly somehow stole 2017 because it’s almost over and I’m sure it was only yesterday that we shared what Endocode achieved in 2016. Yet somehow, here we are and a lot has happened in 2017. We continued to shape our concept of life-long learning in tech in the Endoctus Academy, and started a new initiative to improve the overall state of FOSS compliance.
