Comments
Sort by recent activity
Thanks, I believe I have been able to successfully adjust our deployment script to account for this. / comments
Thanks, I believe I have been able to successfully adjust our deployment script to account for this.
Just echoing that we are also waiting for a fixed version of SQL prompt at our organization as well. / comments
Just echoing that we are also waiting for a fixed version of SQL prompt at our organization as well.
Looks like I just crossed paths with the update notification: I've got v13.0.54 installed and can confirm it has updated the custom alerts. / comments
Looks like I just crossed paths with the update notification: I've got v13.0.54 installed and can confirm it has updated the custom alerts.
So after some actual sleep I need to apologize (and thank you for the magic eyes). We had configured a library variable for the SQL Compare options. Octopus deploy was overwriting the local variable with the default from the library. Was able to retest and confirm that it is working as expected. Thank you! / comments
So after some actual sleep I need to apologize (and thank you for the magic eyes). We had configured a library variable for the SQL Compare options. Octopus deploy was overwriting the local variabl...
@Pete_Ruiz , I have a deployment filter defined and included in the step but it doesn't currently prevent changes to the dbo schema when I deploy. (I've attached the scpf file as a txt) / comments
@Pete_Ruiz , I have a deployment filter defined and included in the step but it doesn't currently prevent changes to the dbo schema when I deploy. (I've attached the scpf file as a txt)
Apparently I had 3 different versions of git installed somehow (?) none of them were current. I had to uninstall them (and rip one out manually) and start from scratch. It even slowed our software architect down a bit tryi / comments
Apparently I had 3 different versions of git installed somehow (?) none of them were current. I had to uninstall them (and rip one out manually) and start from scratch. It even slowed our software ...
We're experiencing something similar I think (although with SQL Change Automation now)? The default filter is being picked up just fine but we have a deployment filter in the same location (db/state/ in the nuget package) we'd like to specify when deploying our package. When we pass in the file name to the Octopus Deploy "Deploy from Package" job step the step will fail with an error that the specified filter cannot be found in the working directory. / comments
We're experiencing something similar I think (although with SQL Change Automation now)? The default filter is being picked up just fine but we have a deployment filter in the same location (db/stat...
Actually @AlexYates was came up with the answer I was looking for on SQL Community slack: the path to the alternative filter is absolute (or defaults the working directory). As the filter was in the nuget package we had to use #{Octopus.Action[Package Self Deployment].Output.Package.InstallationDirectoryPath}\db\state\<filter file> which created an absolute path from C:\ to where the tentacle unpacked nuget. / comments
Actually @AlexYates was came up with the answer I was looking for on SQL Community slack: the path to the alternative filter is absolute (or defaults the working directory). As the filter was in th...
This would be a nice addition to the other tools as well (if the work done for SQL monitor can be ported to them) such as SQLClone / comments
This would be a nice addition to the other tools as well (if the work done for SQL monitor can be ported to them) such as SQLClone
I am experiencing this problem still as well. / comments
I am experiencing this problem still as well.