I'm new to TeamCity and want to use it to start using it as the CI solution for open-source project. So far, so good, but there's one problem I'm having. The unit tests for the project use an .xml file to get some user-specific configuration options (usernames & passwords amongst them)
Up until now, we've included an project file entry for setup.xml (the file in question) but omitted it from source control, the idea being that users get the source and want to run the tests provide their own version with their own usernames and passwords to run the tests as.
This is problematic for me now, as I want TeamCity to run the tests, obviously, but I'm at a loss as to how to provide it the appropriate version of the setup.xml file without adding it to SCC.
I've looked for a pre-build step option where I could use a script of some sort to add it in the appropriate location but don't see anything like that. I've also considered a second project that has that file as its output and is listed as a dependency of the main project, but that feels like overkill. (As is writing a plugin, something I've also considered and dismissed).
I'm hoping I'm overlooking an obvious solution due to my nubness.