text
stringlengths
0
1.8k
[1044.38 --> 1044.92] to be able
[1044.92 --> 1046.00] to use
[1046.00 --> 1046.56] this pipeline
[1046.56 --> 1047.34] execution data
[1047.34 --> 1047.98] to do some
[1047.98 --> 1048.72] cost accounting
[1048.72 --> 1049.56] then you need
[1049.56 --> 1050.40] to associate
[1050.40 --> 1051.02] attribute
[1051.02 --> 1051.68] your pipeline
[1051.68 --> 1052.10] execution
[1052.10 --> 1052.68] to a team
[1052.68 --> 1053.08] so maybe
[1053.08 --> 1053.76] it's to understand
[1053.76 --> 1055.00] what has caused
[1055.00 --> 1055.56] your pipeline
[1055.56 --> 1056.46] we are improving
[1056.46 --> 1057.16] this on Jenkins
[1057.16 --> 1057.72] at the moment
[1057.72 --> 1058.90] how to understand
[1058.90 --> 1059.70] what caused
[1059.70 --> 1060.22] the execution
[1060.22 --> 1060.96] of a pipeline
[1060.96 --> 1061.48] to be able
[1061.48 --> 1062.08] to attribute
[1062.08 --> 1062.82] it to the right
[1062.82 --> 1063.12] team.
[1063.48 --> 1064.76] Same will be
[1064.76 --> 1065.72] for using
[1065.72 --> 1066.38] the pipeline
[1066.38 --> 1067.26] execution data
[1067.26 --> 1068.48] to understand
[1068.48 --> 1069.46] the velocity
[1069.46 --> 1070.06] of teams
[1070.06 --> 1070.92] on the software
[1070.92 --> 1072.06] delivery process
[1072.06 --> 1073.62] in different
[1073.62 --> 1074.88] CI platforms
[1074.88 --> 1076.50] on your pipelines
[1076.50 --> 1077.36] you have some
[1077.36 --> 1078.14] concepts that are
[1078.14 --> 1079.12] commonly used
[1079.12 --> 1080.14] to define
[1080.14 --> 1080.86] your business
[1080.86 --> 1081.34] logic
[1081.34 --> 1082.02] in Jenkins
[1082.02 --> 1082.68] people commonly
[1082.68 --> 1083.60] use what they
[1083.60 --> 1084.12] call stages
[1084.12 --> 1085.32] which is grouping
[1085.32 --> 1086.16] of things
[1086.16 --> 1086.72] it's maybe
[1086.72 --> 1087.82] the CI build
[1087.82 --> 1088.34] phase
[1088.34 --> 1089.24] it's a QA
[1089.24 --> 1090.20] validation phase
[1090.20 --> 1091.14] it's a security
[1091.14 --> 1092.18] validation phase
[1092.18 --> 1092.98] and so here
[1092.98 --> 1093.54] we need to
[1093.54 --> 1094.12] capture the
[1094.12 --> 1095.02] right attributes
[1095.02 --> 1096.30] on this
[1096.30 --> 1097.38] construct of
[1097.38 --> 1098.14] the pipelines
[1098.14 --> 1098.92] that are used
[1098.92 --> 1100.42] for organizational
[1100.42 --> 1100.90] grouping
[1100.90 --> 1101.88] to be sure
[1101.88 --> 1102.54] that the data
[1102.54 --> 1103.62] will be useful
[1103.62 --> 1104.68] downstream
[1104.68 --> 1106.18] for the consumers
[1106.18 --> 1107.06] the use case
[1107.06 --> 1107.72] that will come
[1107.72 --> 1108.16] one day
[1108.16 --> 1124.86] what's going on
[1124.86 --> 1125.16] shippers
[1125.16 --> 1125.94] our friends
[1125.94 --> 1126.78] at Fastly
[1126.78 --> 1127.18] are running
[1127.18 --> 1128.14] an amazing promo
[1128.14 --> 1128.84] with massive
[1128.84 --> 1129.36] savings
[1129.36 --> 1130.18] on compute
[1130.18 --> 1131.00] at edge
[1131.00 --> 1131.78] they're inviting
[1131.78 --> 1132.22] our entire
[1132.22 --> 1132.72] listener base
[1132.72 --> 1133.04] to move
[1133.04 --> 1133.42] latency
[1133.42 --> 1133.84] sensitive
[1133.84 --> 1134.36] workloads
[1134.36 --> 1135.02] to the
[1135.02 --> 1135.46] edge
[1135.46 --> 1136.10] with compute
[1136.10 --> 1136.68] at edge
[1136.68 --> 1137.02] free for
[1137.02 --> 1137.60] three months
[1137.60 --> 1138.56] plus up to