I'm writing a Custom Build Trigger to start a full build of our code after a failed Continuous Integration build. Currently, the implementation of finding the associated full build configuration relies on some very weak assumptions. It would require the two Build Configurations (our CI/Full builds are separted by Build Configs), and a certain set of build parameters must match. Ideally, I would really like a model similar to the Full Build Trigger implementation. This would allow the user to add this trigger to any configuration with much more ease. This would also make the code much more portable, allowing this to be shared. Lastly, the build configurations wouldn't necessarily have to be in the same parent project.
Does anyone know how I would go about implementing this in my editBuildTrigger file? I understand this is not part of the Open API, but we are not immediately worried about upgrading in the near future.
TeamCity 7.0.2 (build 21349)
PS: If you aren't familiar with the Full Build Trigger, I've attached a screenshot of the selection screen. The string before the "::" is the project, the string after is the build configuration.