text
stringlengths
0
1.8k
[842.24 --> 843.12] what happens,
[843.28 --> 844.90] what are the cost blockers,
[845.08 --> 845.56] for example,
[845.80 --> 846.82] what are the obstacles
[846.82 --> 848.22] our system experiences.
[848.94 --> 850.46] And it gets complicated
[850.46 --> 851.04] even more
[851.04 --> 851.80] when we talk about
[851.80 --> 852.36] priorization.
[852.82 --> 853.36] So basically,
[853.56 --> 854.58] for each build,
[854.70 --> 856.20] we need a distributed trace
[856.20 --> 857.88] for going deep
[857.88 --> 858.74] and hence,
[858.86 --> 859.68] passing context
[859.68 --> 860.36] through a level
[860.36 --> 861.00] of the systems
[861.00 --> 861.80] is essential.
[862.50 --> 863.06] I wouldn't say
[863.06 --> 863.76] that this question
[863.76 --> 864.62] is fully resolved
[864.62 --> 865.12] by now
[865.12 --> 866.28] and I want to see
[866.28 --> 867.10] much more happening
[867.10 --> 867.72] on this state.
[868.06 --> 869.16] But my expectation
[869.16 --> 869.74] as a user
[869.74 --> 871.34] to have full observability
[871.34 --> 872.26] for pipeline
[872.26 --> 873.64] as a single trace
[873.64 --> 874.86] for all levels.
[875.24 --> 876.30] And I'm looking forward
[876.30 --> 877.22] to see a system
[877.22 --> 878.54] that actually does that.
[878.68 --> 879.30] So we understand
[879.30 --> 880.38] when the pipeline starts
[880.38 --> 881.80] and what happens
[881.80 --> 882.56] at the beginning.
[882.76 --> 883.86] The middle is always
[883.86 --> 884.44] a bit hazy
[884.44 --> 885.58] so we can leave it like that
[885.58 --> 886.70] because it depends
[886.70 --> 887.80] on what it needs to do.
[887.98 --> 889.04] But I think that we all agree
[889.04 --> 889.90] that when the pipeline
[889.90 --> 890.66] ends,
[891.02 --> 891.80] some artifact,
[892.14 --> 893.06] maybe production artifact,
[893.06 --> 894.38] need to be produced.
[894.38 --> 894.78] Yes.
[895.20 --> 895.56] Now,
[895.66 --> 896.88] I know that some teams
[896.88 --> 898.34] like their pipeline
[898.34 --> 899.76] to end with code
[899.76 --> 900.78] actually being deployed
[900.78 --> 901.44] into production.
[901.64 --> 902.66] What do you think about that?
[902.72 --> 903.28] Do you think that
[903.28 --> 904.32] that should be the last step
[904.32 --> 904.84] of the pipeline?
[904.98 --> 905.42] Do you think
[905.42 --> 906.66] about this differently?
[907.16 --> 907.34] Well,
[907.44 --> 908.18] it depends whether
[908.18 --> 909.56] it's CI, CD pipeline
[909.56 --> 910.84] because in CD pipeline
[910.84 --> 911.98] we usually deploy
[911.98 --> 913.26] as the last stage
[913.26 --> 914.22] in CI pipeline
[914.22 --> 915.36] even if we deploy
[915.36 --> 916.00] the last stage
[916.00 --> 916.78] is actually doing
[916.78 --> 918.10] a lot of reporting
[918.10 --> 919.30] and post-processing
[919.30 --> 920.78] because it's not enough
[920.78 --> 922.26] to deliver the software.
[922.26 --> 922.98] we also need
[922.98 --> 923.82] to do a lot
[923.82 --> 924.86] of accounting work
[924.86 --> 925.52] afterwards.
[925.82 --> 926.46] We also need
[926.46 --> 928.32] to process the results,
[928.48 --> 928.92] compare them
[928.92 --> 929.98] with previous runs,
[930.16 --> 931.62] publish whatever coverage,
[931.76 --> 932.46] test reports,
[933.04 --> 934.40] and many of the things
[934.40 --> 935.56] happen post-factum.
[936.00 --> 937.00] Deployment is definitely
[937.00 --> 937.42] important
[937.42 --> 938.46] for any kind
[938.46 --> 939.32] of modern pipeline.
[939.88 --> 940.58] There are many
[940.58 --> 942.32] other activities
[942.32 --> 943.82] and task-heavy activities
[943.82 --> 944.68] which still need
[944.68 --> 945.22] to be delivered.
[945.68 --> 946.16] And all of that
[946.16 --> 947.16] involves many
[947.16 --> 948.20] of external tools