According to the docs, the teamcity integration needs a "build configuration id". Since this is something attached to each project it doesn't make sense - I would assume that node-build-monitor is able to monitor all builds on a teamcity server and not just a single one? I've tried setting it to "*" but that didn't do anything. It would be great if configuration items were clarified (both in terms
The Dockerfile sets NUGET_XMLDOC_MODE=skip. I can see that this would help performance. However, I can find no general TeamCity documentation that advises making this change on build agents. Therefore it would seem likely that this is not set on most users' non-Docker-based agents. And so it seems odd that it would be set on the Docker image, which, arguably, should represent the typical agent
It would be useful to have a data source for git_vcs_root, to allow attaching a VCS Root from a parent project into a project created by this resource.
Custom pod template description is always "Custom pod template"
Would be nice if it matched the agent name prefix or if there was a description field available to differentiate between multiple templates
It would be really nice if a sample were provided that supports running PostGres/SqlServer depending on the platform. This would help provide a production like environment.
According to the docs, the teamcity integration needs a "build configuration id". Since this is something attached to each project it doesn't make sense - I would assume that node-build-monitor is able to monitor all builds on a teamcity server and not just a single one? I've tried setting it to "*" but that didn't do anything. It would be great if configuration items were clarified (both in terms