Logger for LogRoleReplace
When we have tried it for a while we can consider implement it as a logger to get the replaced output directly.
An alternative would also be to run it as a post job in jenkins (tricky to read the consoleText and save the replaced output somewhere in the build directory, still accessible from the web-ui).
An alternative would also be to run it as a post job in jenkins (tricky to read the consoleText and save the replaced output somewhere in the build directory, still accessible from the web-ui).
Leave a comment
on 2012-07-05 13:53 *
By viktorklang
Milestone changed from Infrastructure and Framework For Distributed and Load Testing to Coltrane
I think it works fine as is.
Updating tickets (#620, #679, #725, #750, #752, #753, #754, #763, #789, #870, #893, #922, #953, #954, #971, #977, #983, #985, #987, #991, #1026, #1045, #1051, #1060, #1061, #1084, #1098, #1099, #1133, #1134, #1135, #1136, #1137, #1194, #1225, #1226, #1243, #1245, #1247, #1248, #1254, #1261, #1300, #1317, #1391, #1412, #1791, #1793, #1901, #1908, #1911, #1912, #1913, #1914, #1915, #1916, #1917, #1922, #1983, #1987, #1996, #1997, #1998, #2066, #2077, #2105, #2117, #2133, #2143, #2149, #2151, #2152, #2153, #2155, #2157, #2158, #2159, #2160, #2161, #2162, #2163, #2164, #2165, #2167, #2171, #2175, #2176, #2177, #2180, #2182, #2184, #2185, #2193, #2199, #2202, #2204, #2206, #2207, #2209, #2210)