Feature requests: Expand to FB failed action, show FB action duractions

Continua CI Feature Requests
1

I have two small feature requests that would make using Continua CI + FinalBuilder a bit more pleasant:

  1. We have a FinalBuilder script with a try..except where if an action fails we send an email and then does a “Stop Run [Failure]”. Within the Continua CI interface, it can take quite a bit of clicking to navigate down to the action that actually failed. It would be nice if there were some easier way to expand the tree of the embedded FinalBuilder log down to the action that failed.
  2. It would likewise be nice if the embedded FinalBuilder log showed the durations for the embedded actions, rather than just showing the duration of the FB execution as a whole. Could be less of a problem if/when you’re able to launch Linux/macOS build agents, but at least right now, since we used to use the FB webserver for builds, the entirety of our Continua CI execution is a single FinalBuilder action.
2

Hi Zoë

You can solve both of those problems by exporting the finalbuilder log and adding it as a report in Continua CI. It’s really easy to do

image
image913×345 13.9 KB

The exported log is easier to navigate and it’s searchable (choose the Tree style).

image
image937×543 22.5 KB

3

Nice!

Is it intended that the “Duration” column doesn’t include the times for their nested actions? I can understand why it’s that way, but it does make it harder to get a feel for where things can be sped up if you have to descend down 6 subnodes of 00:00:00 before seeing 00:25:03. I do see that that matches the FinalBuilder GUI.

Also, and I fully expect a “no and will never be added” here, but that 25 min action is a complex shell script we’re executing over SSH that produces 37000 lines of output. We can’t really split it up into multiple actions. Is there anything we could add to the logged output that FinalBuilder could detect to make artificial subnodes or something to make the output more manageable? Say something like “echo [FinalBuilder: Start action A]” followed by a “echo [FinalBuilder: End action A]” once a lengthy step is done?

4

The timing resolution is 1ms so actions that take less than that will show 0.00

Continua CI does support custom log messages

I am pretty sure Finalbuilder passes those through to Continua

I can’t test right now as I am off work with a back injury

5

About your big log issue -

I’d try to have FinalBuilder save the output of the ssh script to a file on the Continua CI agent workspace and use workspace rules to transfer it to the server - then register the file as a report for the CI build.

This way it would appear as another, separate report in a tab next to the FinalBuilder log report.