Please log in to watch this conference skillscast.
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:
- Test Driven Development: That’s Not What We Meant (SkillsCast recorded in December 2017)
- Certified Large-Scale Scrum Practitioner: Principles to Practices (In Person) with Ben Maynard (in London on 16th - 18th August 2021)
- Large-Scale Scrum In-Person Courses Bundle with Ben Maynard (in London on 16th - 20th August 2021)
- The Study of Enterprise Agility Community: Global Enterprise Agility Month — Delivery Week (Online Conference on 27th - 29th July 2021)
- P3X — People Product Process eXchange 2021 (Online Conference on 8th - 9th September 2021)
- The What & Why of Continuous Discovery (Online Meetup on 27th July 2021)
- Team Identity and its Impact on an Organisation (Online Meetup on 3rd August 2021)
- Storytelling: Shifting the Culture Through Sharing Experiences (SkillsCast recorded in July 2021)
- How To Make Loveliness (SkillsCast recorded in July 2021)
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.