Add flow node log

[panicking]

Related to #61

Navigate the node to find the first one that show the error. This limit the log to the minimal in the pipeline.

Testing done

This done on multistage pipeline, where the log was printed to check if was correspoding to the the expected one

[panicking]

@jenkinsci/explain-error-plugin-developers Can I ask to use the rebase and merge without squash? It's important for people that join the project to understand each commit and the reason why they get splitted.

[shenxianpeng]

Thanks for your suggestion. Currently, our pull request merge messages are set as follows:

For squash merges, we chose the default commit message option "Pull request title and description" instead of "Pull request title and commit details", as it seems easier to provide a useful description here than in individual commit messages. Additionally, many people tend to write commit messages without a detailed body.

I understand your point. We can consider doing this in cases when individual commits is important. For most PRs, however, squash merges help keep the main branch history cleaner.