SQL Automation configuration parameter issues
Cameron.Watson
Posts: 6
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.
Cheers,
Cameron
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.
Cheers,
Cameron
Comments
For the latter query - error reports - you cannot currently turn this off. It's logged as a request here (ref. SQLCI-95) but it's not been implemented thus far.
As for the former, the server/db relate to the ones that are updated on each build but I don't have a clue as to why we add those. My guess would be they need to be parameters in that way to be passed to the command-line but I don't know for sure. I've asked the development team if they can shed any light on it and I'll post back when I hear something.
Redgate Software
Redgate Software
So given your information, should I assume that the parameters are passed in at runtime, and not hard-coded in? I currently use an environment parameter on the build configuration to set the destination server. This is passed into the redgate build steps as a parameter in it's configuration. I'm assuming that this value is set at runtime, and not at the initial configuration?
Redgate Software
I just ran a test with it to see what it would do if you ran it with mismatching env and config variables. It updated the conf variables to match the env variable and then processed. So it seems as though it is at run time, but it's very confusing if you plan to change your variables often. Intuitively, you think you should change all of them.
Redgate Software