SQL Automation configuration parameter issues

Cameron.WatsonCameron.Watson Posts: 6
edited December 19, 2013 10:19AM in SQL Compare Previous Versions
Apologies for the cross-post. I posted this under the Deployment Manager group as well as there is no specific SQL Automation forum.

I've been testing out the SQL Automation plugin for Teamcity this week and have run into a couple of issues that I'd like some help with.

The first is to do with build parameters. We use a number of environment variables in our build process to set destination servers & paths. We've noticed that the automation plugin seems to add some new configuration parameters as well. They all have the name of "Requires Exclusive Use of #" and contains a server/database name pair in the value.

Could someone explain what is happening with these? If I remove them, they keep reappearing every time we run a build.

Secondly, when we have a build failure from a database error, the redgate CI engine triggers an error too stating that it can't connect to the remote redgate centre to report the error. Our server sits behind a firewall and doesn't have external access, is there a way to turn this off?

If you need more information or a copy of any logs or screenshots, I can provide them for you.

Sign In or Register to comment.