text stringlengths 0 1.8k |
|---|
[948.20 --> 949.40] because you can |
[949.40 --> 950.82] deploy to other tools. |
[950.96 --> 951.54] For reporting |
[951.54 --> 952.54] you may use |
[952.54 --> 953.56] external tools |
[953.56 --> 955.10] like test trail |
[955.10 --> 956.72] it can be on-premise |
[956.72 --> 957.70] but still |
[957.70 --> 958.58] when something |
[958.58 --> 959.16] goes wrong |
[959.16 --> 960.06] you will need |
[960.06 --> 961.06] to access this data |
[961.06 --> 961.94] and you will need |
[961.94 --> 962.46] to understand |
[962.46 --> 963.04] where it went. |
[963.26 --> 963.90] What do you think, Cyril? |
[964.02 --> 964.70] I would like to |
[964.70 --> 965.94] come back to your question |
[965.94 --> 967.44] on what is the right way |
[967.44 --> 968.72] to instrument a pipeline. |
[969.06 --> 970.36] What we have discovered |
[970.36 --> 971.98] instrumenting |
[971.98 --> 972.80] Jenkins |
[972.80 --> 973.68] on Maven |
[973.68 --> 974.56] on Ansible |
[974.56 --> 975.88] is that |
[975.88 --> 976.80] instrumenting |
[976.80 --> 978.02] well your pipeline |
[978.02 --> 979.04] is a journey |
[979.04 --> 980.34] for the instrumentation |
[980.34 --> 980.72] people. |
[981.24 --> 982.08] We have to |
[982.08 --> 982.92] understand |
[982.92 --> 983.98] what are the right |
[983.98 --> 985.28] spans to capture |
[985.28 --> 986.62] in your pipeline execution |
[986.62 --> 987.46] to capture |
[987.46 --> 988.38] the right step. |
[989.02 --> 989.72] For example |
[989.72 --> 990.84] on Jenkins |
[990.84 --> 991.92] we had to iterate |
[991.92 --> 992.76] to capture |
[992.76 --> 994.24] the right spans |
[994.24 --> 995.32] to measure |
[995.32 --> 996.00] the time |
[996.00 --> 996.68] it was taken |
[996.68 --> 997.48] to allocate |
[997.48 --> 998.28] the build agent. |
[998.68 --> 999.46] Our initial |
[999.46 --> 1000.28] instrumentation |
[1000.28 --> 1000.96] did not capture |
[1000.96 --> 1001.44] it well |
[1001.44 --> 1002.64] so it was hard |
[1002.64 --> 1004.06] for CICD administrators |
[1004.06 --> 1005.30] to really |
[1005.30 --> 1006.10] narrow down |
[1006.10 --> 1006.88] their investigation |
[1006.88 --> 1008.02] to this specific |
[1008.02 --> 1008.42] phase |
[1008.42 --> 1009.28] on understanding |
[1009.28 --> 1010.22] and evolving |
[1010.22 --> 1011.00] across time. |
[1011.66 --> 1012.26] Another thing |
[1012.26 --> 1013.02] that was important |
[1013.02 --> 1013.40] for us |
[1013.40 --> 1014.58] was to iterate |
[1014.58 --> 1015.38] on the right |
[1015.38 --> 1016.20] attributes |
[1016.20 --> 1017.00] we extract |
[1017.00 --> 1017.72] from the pipeline |
[1017.72 --> 1018.22] execution |
[1018.22 --> 1019.60] that we attach |
[1019.60 --> 1020.38] to the spans |
[1020.38 --> 1021.64] so that you can |
[1021.64 --> 1022.84] get the right |
[1022.84 --> 1023.42] meaning |
[1023.42 --> 1024.34] of the data |
[1024.34 --> 1025.72] for your use case. |
[1026.34 --> 1027.08] We've seen |
[1027.08 --> 1028.36] that there is |
[1028.36 --> 1029.14] a troubleshooting |
[1029.14 --> 1029.80] use case |
[1029.80 --> 1030.32] troubleshooting |
[1030.32 --> 1031.18] of your pipeline |
[1031.18 --> 1031.68] execution |
[1031.68 --> 1032.78] so here maybe |
[1032.78 --> 1033.48] you need to |
[1033.48 --> 1034.08] capture |
[1034.08 --> 1034.42] well |
[1034.42 --> 1035.46] the GitHub |
[1035.46 --> 1036.26] access |
[1036.26 --> 1037.50] GitHub URL |
[1037.50 --> 1039.04] your Jira URL |
[1039.04 --> 1039.92] sometime |
[1039.92 --> 1040.84] you need to |
[1040.84 --> 1041.18] capture |
[1041.18 --> 1041.54] some |
[1041.54 --> 1042.26] organizational |
[1042.26 --> 1043.18] information |
[1043.18 --> 1044.38] if you want |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.