text
stringlengths
0
1.8k
[712.46 --> 713.14] previously.
[713.72 --> 714.28] These people,
[714.38 --> 715.08] they are very interested
[715.08 --> 716.60] in having an abstraction
[716.60 --> 718.40] to look at the CD process
[718.40 --> 720.06] rather than the details
[720.06 --> 721.66] of each CI tool.
[722.22 --> 723.30] On this culture
[723.30 --> 725.66] of the open telemetry community
[725.66 --> 727.54] of creating semantic conventions
[727.54 --> 728.78] that spans across
[728.78 --> 729.74] different tools,
[729.90 --> 730.42] techniques,
[730.60 --> 731.28] implementations,
[731.28 --> 733.42] I think is a very good match
[733.42 --> 734.44] with the problems
[734.44 --> 735.22] we want to solve.
[735.76 --> 737.24] So I saw these two dimensions,
[737.60 --> 738.34] collecting data
[738.34 --> 740.24] and also this culture
[740.24 --> 742.08] of abstracting
[742.08 --> 744.64] to provide a unified vision
[744.64 --> 745.92] on top of different
[745.92 --> 747.48] implementation details
[747.48 --> 748.26] in some ways.
[748.90 --> 749.90] So from the perspective
[749.90 --> 752.64] of having a good CI-CD system,
[752.86 --> 753.80] regardless whether it's one
[753.80 --> 754.36] or multiple,
[754.78 --> 756.26] which has a good
[756.26 --> 757.98] open telemetry integration,
[758.50 --> 760.30] what would that look like
[760.30 --> 760.96] from the moment
[760.96 --> 762.22] you push some code?
[762.46 --> 764.08] What is like the perfect flow
[764.08 --> 764.90] that you imagine
[764.90 --> 765.96] that a system
[765.96 --> 767.02] with good open telemetry
[767.02 --> 767.76] would have?
[767.76 --> 769.04] Yeah, so first of all,
[769.16 --> 770.14] pipeline would include
[770.14 --> 771.50] multiple tools in the chain.
[772.06 --> 772.64] So for example,
[772.78 --> 773.88] we push the code,
[774.00 --> 775.62] it reaches firstly,
[775.94 --> 777.76] whatever social coding system,
[777.88 --> 778.62] let's say GitHub,
[778.90 --> 779.40] GitLab.
[779.40 --> 780.62] Even on this level,
[780.74 --> 781.84] there are some events happening.
[782.14 --> 782.44] Firstly,
[783.00 --> 784.34] the system needs to process
[784.34 --> 785.06] your request.
[785.24 --> 786.20] It may apply some
[786.20 --> 787.02] its own checks,
[787.12 --> 787.48] for example,
[787.64 --> 788.74] via GitHub actions,
[788.92 --> 789.22] et cetera.
[789.74 --> 790.70] And after that,
[791.10 --> 792.60] our main CI starts
[792.60 --> 793.60] or CD.
[794.28 --> 795.02] So we invoke
[795.02 --> 796.24] external service.
[796.46 --> 796.68] Again,
[796.78 --> 798.18] we may send webhooks
[798.18 --> 799.84] to completely different instance.
[800.00 --> 801.10] This instance provision
[801.10 --> 803.00] whatever our build executor,
[803.12 --> 804.40] it may be called the agent,
[804.70 --> 806.04] it may be just a new
[806.04 --> 807.68] whatever pipeline task
[807.68 --> 809.02] definition in Tecton
[809.02 --> 810.12] in a separate container,
[810.28 --> 810.84] it starts.
[811.48 --> 812.72] And then we just start
[812.72 --> 813.72] executing pipeline.
[814.22 --> 815.26] And at this level,
[815.62 --> 816.52] it's also not the end
[816.52 --> 818.00] because then we invoke tools
[818.00 --> 819.84] because nobody really
[819.84 --> 821.10] builds software
[821.10 --> 822.70] in CI or CD systems.
[822.92 --> 823.88] It's external tools
[823.88 --> 825.02] like Maven or Gradle
[825.02 --> 825.64] doing that,
[825.76 --> 826.40] you invoke them.
[826.88 --> 827.58] So these tools
[827.58 --> 828.56] are also complicated
[828.56 --> 830.12] and you also need to have
[830.12 --> 831.62] observability on this level.
[831.90 --> 832.40] So basically,
[832.84 --> 833.44] in the beginning
[833.44 --> 834.20] of this pipeline,
[834.30 --> 835.14] we should go through
[835.14 --> 836.90] all these levels of tools
[836.90 --> 838.02] and for each level,
[838.18 --> 838.44] ideally,
[838.60 --> 839.74] we need to have
[839.74 --> 840.84] some data
[840.84 --> 842.24] so that we can understand