text stringlengths 0 1.8k |
|---|
• Importance of standardizing CI/CD processes, managing them as a "kettle" rather than individual "pets" |
• Security considerations for build systems and production environments |
• Supply chain security within the CICD space and importance of dependency updates and scanning |
• Open telemetry instrumentation for continuous delivery pipelines |
• Audit trails and logs management for release and build processes |
• Importance of capturing accurate information in the bill of material |
• Verification and trust requirements for Jenkins and CI systems |
• Incremental journey of verifying captured data and metadata on builds |
• Integration of Captain Obvious with OpenTelemetry and Jenkins |
• Exposure of quality gate information to enable verification |
• Plans for integrating Captain with other tools and systems |
• Update on the status of Captain Obvious project, including its integration into Cloud Native Computing Foundation |
• Discussion of the vibrant community surrounding Captain Obvious |
• Discussion about living in Switzerland |
• Open source standard "open telemetry" for observing CICD pipelines |
• Importance of exposing data from CICD processes |
• Data analysis for optimizing pipelines and decision-making |
• Standardization of open telemetry events |
• Adoption and growth of the open telemetry ecosystem |
• Future plans for donating code to the open telemetry community |
• Progress on open telemetry Ansible integration |
• Donating Ansible integration to the community |
• Iterating and rolling out inside Elastic |
• Jenkins evolution roadmap to be published soon |
• Future projects in observability and open source |
[0.08 --> 5.52] I'm your host, Gerhard Lassi, and you're listening to Ship It, a podcast about code, |
[6.02 --> 9.72] ops, infrastructure, and the people that make it happen. |
[10.18 --> 16.48] Yes, we focus on the people and what happens when their best ideas meet the real world. |
[17.08 --> 17.34] Why? |
[17.74 --> 23.02] Because that's how we learn, get inspired, and find out what is worth doing. |
[23.26 --> 29.52] Today, I'm joined by Cyril Leclerc, Product Manager, Lead on Observability at Elastic, |
[30.00 --> 33.36] and Oleg Dinashev, Principal Engineer at Cloudbeast. |
[33.80 --> 36.34] It all started with Oleg's tweet back in July, |
[36.64 --> 42.28] in which he was promoting Akihiro Kiuchi's work on Jenkins Monitoring with OpenTelemetry. |
[42.66 --> 45.28] This was done in the context of Google's Summer of Code, |
[45.62 --> 49.10] and there is a video with Akihiro demoing this project in the show notes. |
[49.38 --> 51.42] As you may remember from episode 20, |
[52.00 --> 54.94] instrumenting our changelog.com pipeline is on my mind, |
[55.24 --> 58.62] and this conversation helped me clarify how I'm going to approach it. |
[58.62 --> 60.88] I have learned a lot from Oleg and Cyril, |
[61.24 --> 64.44] and if you're thinking of doing something similar, this episode is for you. |
[64.94 --> 68.70] Big thanks to our partners Fastly, LaunchDarkly, and Linode. |
[69.20 --> 71.04] Thank you for the great bandwidth, Fastly. |
[71.32 --> 73.82] You can learn more at Fastly.com. |
[74.54 --> 79.40] Ship new features with confidence by getting your feature flags powered by LaunchDarkly.com, |
[79.40 --> 83.26] and thank you Linode for keeping our Kubernetes fast and simple. |
[83.82 --> 89.48] You too can run our infrastructure as we do by linode.com forward slash changelog. |
[89.48 --> 99.96] This episode is brought to you by Honeycomb. |
[100.30 --> 103.66] Honeycomb is built on the belief that there's a more efficient way |
[103.66 --> 107.10] to understand exactly what is happening in production right now. |
[107.42 --> 111.22] When production is running slow, it's hard to know exactly where problems originate. |
[111.46 --> 115.44] Is it your application code, your users, or the underlying systems? |
[115.44 --> 120.28] Teams who don't use Honeycomb scroll through endless dashboards guessing at what they mean. |
[120.52 --> 122.88] They deal with alert floods, guessing which ones matter, |
[123.26 --> 126.98] and go from tool to tool to tool guessing at how the puzzle pieces all fit together. |
[127.30 --> 131.42] It's this context switching and tool sprawl that are slowly killing your teams and your business. |
[131.82 --> 134.94] With Honeycomb, you get a fast, unified, and clear understanding |
[134.94 --> 137.70] of the one thing driving your business, production. |
[138.12 --> 140.06] Honeycomb quickly shows you the correct source of issues, |
[140.44 --> 143.42] discover hidden problems, even in the most complex stacks, |
[143.42 --> 146.50] understand why you're at feel slow to only some users. |
[146.96 --> 149.38] With Honeycomb, you guess less and no more. |
[149.82 --> 154.30] Join the swarm and try Honeycomb free today at honeycomb.io slash changelog. |
[154.58 --> 157.26] Again, honeycomb.io slash changelog. |
[157.26 --> 174.30] We are going to ship in three, two, one. |
[174.30 --> 193.32] So, Akihiro Kiyuchi presented Jenkins CI agents monitoring with open telemetry, |
[193.68 --> 196.40] and Jager, Zipkin, and Prometheus was included. |
[196.40 --> 200.96] And one of the goals, or like one of the reasons why I did that, |
[201.36 --> 205.16] was to minimize the downtime and set up costs of Jenkins agents. |
[205.36 --> 208.68] That was like one of the presentation, like the screenshots which I've seen. |
[209.42 --> 214.12] Now, Akihiro couldn't join us today, but we have Cyril and Oleg joining us. |
[214.62 --> 218.50] And we'll be talking about open telemetry in your CI and why is it important. |
[218.50 --> 224.32] And I'm wondering, what can you tell us about the presentation that Akihiro gave back in July, I believe? |
[224.64 --> 225.44] I haven't seen it yet. |
[225.58 --> 226.66] Is it live? Can we watch it? |
[226.78 --> 227.38] Yes, it's live. |
[227.56 --> 232.78] So, it was a project within the Jenkins community as a part of the Google Summer of Code this year. |
[233.44 --> 238.48] Akihiro was one of the students, and he chose visibility with open telemetry. |
[238.78 --> 242.00] Originally, the project was rather positioned towards Prometheus, |
[242.30 --> 244.96] but taking the recent developments and the ecosystem, |
[244.96 --> 251.04] we decided to press it with open telemetry and actually to try all three parts should time allow. |
[251.38 --> 253.98] So, metrics, visibility, and logs. |
[254.12 --> 256.54] For us, it was one of the missing parts of the puzzle |
[256.54 --> 259.68] because we already have open telemetry plugin for Jenkins. |
[260.00 --> 263.52] So, Cyril and many other contributors created it. |
[263.76 --> 267.74] But this plugin focuses on Jenkins controller as one of the instances. |
[268.22 --> 270.92] At the same time, Jenkins itself is a distributed system. |
[270.92 --> 275.58] It has agents, and actually agents may prove to be quite unstable, |
[275.82 --> 278.08] especially if you use multi-cloud environments, |
[278.60 --> 281.58] if you use various cloud provisioning, single-shot agents, |
[281.70 --> 283.32] which are just the day after the completion. |
[283.74 --> 288.12] So, it's essential to have some tracing and monitoring for these systems |
[288.12 --> 292.08] so that you can ensure that your CI environment is operational. |
[292.70 --> 296.40] And of course, if you can also verify that it's cost-effective, it would be super. |
[296.40 --> 302.26] Okay. So, this tracing was happening on the agents, not on the Jenkins master, |
[302.74 --> 306.22] so that when the jobs run, there will be visibility into the jobs |
[306.22 --> 310.24] and into the availability of the agents, of the Jenkins agents themselves. |
[310.38 --> 310.74] Is that right? |
[310.94 --> 311.42] Yes. |
[311.86 --> 312.10] Cyril? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.