Please log in to watch this conference skillscast.
At SpringerNature the development group is adopting microservices. They found that having developers set up build pipelines by hand for each service was time-consuming and led to inconsistencies as our environment changed, so they automated the process.
The team developed a meta-pipeline that will generate a continuous delivery pipeline for any of their repositories that follow a set of conventions - their Meta-Pipeline Protocol.
This will have been presented at SoftwareCircus (Amsterdam), and Agile Cambridge.
Standardising their pipeline definition has greatly reduced the team programmers' effort and allowed them to safely evolve their build environment. They're starting to exploit this meta information to improve their overall environment, for example: to visualise relationships, to manage the running of client contract tests, and to profile build timings.
YOU MAY ALSO LIKE:
- Kito Mann's Hacking HTML5 Web Components and Polymer (in London on 10th - 11th July 2017)
- Lightbend's Fast Track to Akka with Java (in London on 16th - 18th August 2017)
- F# eXchange 2018 (in London on 5th - 6th April 2018)
A meta-pipeline for generating continuous delivery pipelines for microservices
Steve was a pioneer of Agile software development in the UK, he has built applications for banks, ISPs, financial data providers, and specialist software companies. He has given training courses in Europe, America, and Asia.
Hilverd Reker is a developer at Springer Nature in London where he works on the Tools Engineering team. He is identifying and implementing solutions to problems faced by most of Springer’s software development teams, and doing longer-term work that individual teams can find difficult to justify in short-term value. Prior to joining Springer he worked as a Java developer at an online supermarket.