MadsNielsen
commented
7 years ago Talking points
- Explanation of the Eiffel protocol
- Tracey as an external service to generate Eiffel messages
- Microservices / Useful for sharing information
Action points?
- Work towards simplification of generating Eiffel messages (Flemming & Grundfos)
- Graph database to follow events (Flemming & Grundfos & Andrey)
- Provide the appropriate tooling to create events that can be used later (Flemming & Grundfos)
What is tracey
As long as we are compliant with the protocol, then all the different open source protocols can interact.
As a developer you want to know where is your commit in the pipeline
Use cases:
What is important is that it is possible to have multiple different systems listening to each others.
The main problem Flemming is that there is some data that you need to pick up and put into an Eiffel event, and at the moment it is very hard to put that onto the message queue. So we need a framework where we can easily populate a Tracey event with the data that we know how to get.
We have a plugin for BitBucket.
It should be easy to apply your domain knowledge.
Andrey suggest focusing on the integrations. For instance a Gradle plugin.
Will the visualization of the pipeline be possible in the next 6 months? * Well maybe we don't have the pipeline anymore, we rather have chains of events. Or graphs. Where each artifact has a unique graph.
Is there a plugin for ElasticSearch? * There should be
Could we make a translator, for instance so we can ping for instance prometheus endpoints? * Yes, it will be good to use existing tools also
It's not just the build system? * No, it can be anything.
Can it be a requirement sending a message? So we have a full trace? * Yes, that should be the end goal. But it will be a journey to get there
It could for instance be a tiny tool listening to files in a folder, and when a worddocument is there, it will trigger a Jenkins job.
Instead of writing a plugin for JEnkins to do everything you want, you can just have the best tool for the task and have that listen to the RabbitMQ.
There is a benefit from just being able to integrate generic tools.
The Jenkins plugin could be polished a bit, but it basically works.
The generator can be a part of the tool, or it could be a standalone generator ( or both! ).