3

I have defined a process that consists of 2 steps:

  1. Deploy an IIS WebSite
  2. Execute a script file

The first step in the process executes without any issues. I am able to upload a nuget package to Octopus Server's built-in package repository and deploy this to my IIS Web Site.

For the second step in the process, where I am asked to specify a script file to run, I am unable to upload a sql file either using the built-in package repository or using a external package repository since Octopus will not allow me to upload a .sql file type.

What is the best way of specifying the SQL Script File to be run?

Should I package it along with my nuget package and then specify the script source to 'Script file inside a package' or is it possible to upload a SQL file to a repository (external or built-in) and specify that file as the SQL script file to execute?

Is there a best practice for this?

Thanks,

Sean

1
  • 1
    Is that sql file logically part of the website? Could it not be packaged as part of the same NuGet package as the website? Commented May 16, 2017 at 11:27

1 Answer 1

1

By "Script file" or "Script file inside a package" Octopus means a Powershell script or Bash script. If you want to execute a SQL script as part of your deployment you have two options:

  1. Install an existing task from the Octopus Community Library (https://library.octopusdeploy.com/listing) that executes SQL. Here are two of them:

  2. Create a Powershell or Bash script to execute your SQL script.

Sign up to request clarification or add additional context in comments.

2 Comments

Can you provide more information about #2? Code would be nice.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.