how are you using build chain visualizations that CIs like TeamCity and Jenkins offer?
It seems as if I need to “drop” the built-in control flow of gradle in order to have a proper visualization.
Instead of one command ‘gradle check’ I have to “split” the automatic workflow of gradle and define different build steps like “unit testing”, “integration testing”, “functional testing”, … or would you slice more coarse-grained?
What is your best practice? How do you slice your steps?