Perl 6 - the future is here, just unevenly distributed

IRC log for #crimsonfu, 2016-12-14

crimsonfu - sysadmins who code

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:18 larsks joined #crimsonfu
20:50 dotplus opinions please? I have several dozens of software engineers who are my "customers". They work on various efforts in and around building a managed OpenStack product/service. We're considering 2 projects to help them engineer better/faster/easier: 1) performance metrics (probably influxdb/grafana) where the MVP would be fed by Jenkins so that we can learn about changes in job timing 2) ELK, where the goal would be to help the engineers ...
20:50 dotplus ... understand exactly why their build failed, without digging through the rabbithole of jenkins triggered-build logs
20:51 dotplus so are either of those MVPable in a week? if both, which would be more valuable?
23:23 JoeJulian #2 should be easily doable in a week and I think any developer would be ecstatic to not have to look at jenkins.
23:25 JoeJulian You can also use #2 to glean performance metrics calcluating mean and standard deviation. You could even include checks against those statistics in your functional testing.
23:26 JoeJulian dotplus
23:41 bear if you use a set of common scripts to run your builds you can do #1 by using your metrics engine's cli tool to emit timing data to your collector
23:42 bear and then #2 becomes a matter of picking the dashboard product that you prefer
23:44 JoeJulian precisely. I've done it with both elk and splunk.
23:44 bear for me splunk, graylog and elk
23:46 bear just remember to tag the data point with the branch name - otherwise you pollute your master branch timings with the random shit that happens to dev branches

| Channels | #crimsonfu index | Today | | Search | Google Search | Plain-Text | summary

crimsonfu - sysadmins who code