text
stringlengths
0
1.8k
[1406.08 --> 1406.28] on
[1406.28 --> 1406.64] other
[1406.64 --> 1407.08] factors
[1407.08 --> 1407.90] for example
[1407.90 --> 1408.50] there might
[1408.50 --> 1409.50] be provisioning
[1409.50 --> 1410.08] of agents
[1410.08 --> 1410.44] if we
[1410.44 --> 1411.22] talk about
[1411.22 --> 1411.82] the original
[1411.82 --> 1412.36] work for
[1412.36 --> 1412.88] monitoring
[1412.88 --> 1413.48] and this
[1413.48 --> 1413.80] agent
[1413.80 --> 1414.34] provisioning
[1414.34 --> 1414.82] doesn't have
[1414.82 --> 1415.04] to be
[1415.04 --> 1415.50] synchronous
[1415.50 --> 1416.16] agents
[1416.16 --> 1416.58] may be
[1416.58 --> 1416.94] shared
[1416.94 --> 1417.26] between
[1417.26 --> 1417.70] different
[1417.70 --> 1418.28] pipelines
[1418.28 --> 1419.14] and hence
[1419.14 --> 1419.70] various
[1419.70 --> 1420.66] outages
[1420.66 --> 1421.38] and issues
[1421.38 --> 1421.98] also
[1421.98 --> 1422.52] will be
[1422.52 --> 1422.80] between
[1422.80 --> 1423.40] multiple
[1423.40 --> 1423.96] pipelines
[1423.96 --> 1424.52] so being
[1424.52 --> 1425.30] able to
[1425.30 --> 1425.74] trace
[1425.74 --> 1426.36] this event
[1426.36 --> 1426.94] would help
[1426.94 --> 1427.28] me as
[1427.28 --> 1427.86] administrator
[1427.86 --> 1428.54] to understand
[1428.54 --> 1429.48] okay this
[1429.48 --> 1430.10] agent is
[1430.10 --> 1430.48] broken
[1430.48 --> 1431.06] for example
[1431.06 --> 1431.48] it has
[1431.48 --> 1431.78] the wrong
[1431.78 --> 1432.30] version of
[1432.30 --> 1432.82] java due
[1432.82 --> 1433.20] to whatever
[1433.20 --> 1433.60] reason
[1433.60 --> 1434.16] and then
[1434.16 --> 1434.96] I can
[1434.96 --> 1435.54] go back
[1435.54 --> 1435.96] understand
[1435.96 --> 1436.68] which pipelines
[1436.68 --> 1437.32] were affected
[1437.32 --> 1438.50] and restore
[1438.50 --> 1439.24] them if
[1439.24 --> 1439.54] needed
[1439.54 --> 1440.92] and adjust
[1440.92 --> 1441.64] my systems
[1441.64 --> 1442.24] reschedule
[1442.24 --> 1443.00] them so that
[1443.00 --> 1443.82] my delivery
[1443.82 --> 1444.76] continues and
[1444.76 --> 1445.96] my development
[1445.96 --> 1446.94] teams do not
[1446.94 --> 1447.26] have those
[1447.26 --> 1447.48] times
[1447.48 --> 1448.06] just one
[1448.06 --> 1448.54] example
[1448.54 --> 1449.20] there are
[1449.20 --> 1449.58] many like
[1449.58 --> 1449.74] that
[1449.74 --> 1450.06] that's a
[1450.06 --> 1450.46] good one
[1450.46 --> 1451.06] one thing
[1451.06 --> 1452.34] that really
[1452.34 --> 1452.80] got me in
[1452.80 --> 1453.24] the past
[1453.24 --> 1453.86] was caching
[1453.86 --> 1454.62] in CI
[1454.62 --> 1455.32] CD systems
[1455.32 --> 1455.98] so when you
[1455.98 --> 1456.30] have some
[1456.30 --> 1456.88] basically some
[1456.88 --> 1457.38] dependencies
[1457.38 --> 1457.92] which have
[1457.92 --> 1458.50] been cached
[1458.50 --> 1459.34] and there's
[1459.34 --> 1460.62] issues related
[1460.62 --> 1461.44] to retrieving
[1461.44 --> 1461.94] data from
[1461.94 --> 1462.44] the cache
[1462.44 --> 1463.64] it's so
[1463.64 --> 1464.46] difficult to
[1464.46 --> 1465.08] even understand
[1465.08 --> 1465.48] that like
[1465.48 --> 1465.82] where does