We use --workflow to run CI steps in TeamCity. This allows us to limit our TeamCity configuration to just one build step of running the workflow. However, as a result of specifying the steps via the single workflow vs individual build steps in TeamCity we lose certain features of TeamCity such as automatic folding of build output by step and performance monitoring reported of each individual step. TeamCity has a feature called “Service Messages” that allow you to manually print to stdout when steps begin and end however there is no good way to accomplish this currently. Ideally would like something along the lines of an optional “message” field for each workflow step where I could print custom messages at the beginning of a workflow step. For example:
{
"name": "teamcity-windows-debug",
"steps": [
{ "type": "configure", "name": "teamcity-windows-debug", "message": "My custom message." },
{ "type": "build", "name": "teamcity-windows-debug-show-ccache-stats", "message": "My other custom message" },
{ "type": "build", "name": "teamcity-windows-debug-install" },
{ "type": "build", "name": "teamcity-windows-debug-show-ccache-stats", "message": "Perhaps allow macro expansion: ${sourceDir}" },
{ "type": "test", "name": "teamcity-windows-debug-slim", "message": "Perhaps support whatever message(...) supports" }
]
}
Personally, even static messages would work for my needs but either supporting macro expansion or being more of a pass-through to CMake’s message(…) function would be even more functional.