text
stringlengths
0
1.8k
[573.38 --> 575.30] of CI and CD pipelines
[575.30 --> 576.00] and processes.
[576.52 --> 577.28] On exposing,
[577.66 --> 578.96] meeting more practitioners
[578.96 --> 580.56] with this proposal,
[580.72 --> 581.90] we discover that
[581.90 --> 584.32] all the data of the CD processes
[584.32 --> 585.48] is a goldmine.
[585.64 --> 586.00] Of course,
[586.12 --> 587.20] CI and CD administrators
[587.20 --> 588.52] are interested in this
[588.52 --> 589.12] to troubleshoot
[589.86 --> 591.10] on maintain up and running
[591.10 --> 592.04] their platform.
[592.40 --> 593.56] They also see benefits
[593.56 --> 595.68] for sizing their platform.
[596.16 --> 597.30] And then we see dev teams
[597.30 --> 598.70] interesting in shortening
[598.70 --> 600.48] their build cycles,
[600.78 --> 602.86] in optimizing their unit tests,
[602.92 --> 603.74] their flaky tests.
[604.24 --> 605.72] We discover people
[605.72 --> 606.92] doing cost accounting
[606.92 --> 607.56] on platform,
[607.74 --> 608.48] people doing,
[608.86 --> 610.64] I've seen process optimization
[610.64 --> 612.28] like digital transformation,
[612.64 --> 613.40] agile transformation,
[613.62 --> 614.24] DevOps transformation.
[614.46 --> 615.14] You want to measure
[615.14 --> 616.30] your lead time.
[616.70 --> 617.00] And here,
[617.08 --> 618.14] this is a source of data
[618.14 --> 619.72] that is very interesting.
[620.50 --> 621.52] So here we see
[621.52 --> 622.68] a lot of value
[622.68 --> 624.38] in capturing this data
[624.38 --> 625.98] on distributed traces,
[626.12 --> 627.34] which is often associated
[627.34 --> 628.26] with open telemetry
[628.26 --> 629.16] is very useful.
[629.66 --> 631.82] Then what you said also
[631.82 --> 632.92] that was very interesting
[632.92 --> 633.44] for me is
[633.44 --> 634.68] you say we want
[634.68 --> 635.62] a unified view
[635.62 --> 636.74] on CI and CD.
[637.34 --> 638.58] And beyond this debate,
[638.68 --> 639.76] is it different tools?
[639.90 --> 640.94] Is it the same tools?
[641.42 --> 642.84] Here is the distributed
[642.84 --> 644.06] trace culture
[644.06 --> 645.64] tells us that we can
[645.64 --> 647.30] have an overall visibility
[647.30 --> 649.00] across different phases
[649.00 --> 650.48] of the cohesive unit.
[650.48 --> 651.58] And so here,
[651.74 --> 653.24] whatever people choose
[653.24 --> 654.14] to structure
[654.14 --> 655.76] their CI and CD phases,
[656.32 --> 657.68] with this visibility
[657.68 --> 658.76] on the process,
[658.82 --> 659.50] we will be able
[659.50 --> 661.14] to make this unified.
[661.44 --> 662.46] Then when you talked
[662.46 --> 663.82] about open telemetry,
[663.96 --> 665.04] I think open telemetry
[665.04 --> 666.92] is a great solution.
[667.58 --> 668.00] First,
[668.10 --> 669.92] it does distributed traces
[669.92 --> 671.14] way well
[671.14 --> 671.66] in a way
[671.66 --> 672.42] that is standardized,
[673.08 --> 674.52] popular for people.
[674.94 --> 675.66] And also,
[675.88 --> 676.66] open telemetry
[676.66 --> 678.28] as the vision
[678.28 --> 679.28] to provide
[679.28 --> 682.02] unified semantic conventions,
[682.44 --> 683.74] a common vocabulary
[683.74 --> 685.54] to unify things together.
[686.04 --> 686.76] And you said,
[686.92 --> 688.66] I can have different CI
[688.66 --> 689.58] on CD systems.
[689.58 --> 691.08] And I remember this week
[691.08 --> 691.78] I was talking
[691.78 --> 694.24] with some CI platform administrators
[694.24 --> 695.16] who told us,
[695.26 --> 697.16] we don't use only Jenkins
[697.16 --> 698.22] in our organization.
[698.40 --> 699.10] Some other people,
[699.20 --> 700.06] they use BuildKai,
[700.20 --> 701.68] they use maybe other tools.
[701.68 --> 703.32] And we want to have
[703.32 --> 704.76] an holistic vision
[704.76 --> 706.56] across all these
[706.56 --> 708.74] where the CI platform
[708.74 --> 710.24] is an implementation details,
[710.36 --> 711.18] which reminds me
[711.18 --> 712.46] your Tiger conversation