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:
- TDD: That's not what we meant talk (SkillsCast recorded in November 2015)
- Certified Scrum Master with Abid Quereshi (Online Course on 24th - 25th February 2021)
- Agile at Scale with Joakim Sundén (Online Course on 1st - 4th March 2021)
- μCon: The Microservices eXchange (Online Conference on 13th - 14th April 2021)
- P3X — People Product Process eXchange 2021 (Online Conference on 15th - 16th September 2021)
- Personal Engineering: Living Well at Work (Online Meetup on 11th March 2021)
- Agile During the Time of Jesus (SkillsCast recorded in December 2020)
- Event-Driven Microservices: The Sense, Nonsense and a Way Forward (SkillsCast recorded in December 2020)
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.