New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script step embedded in a NuGet package #2189

Closed
PaulStovell opened this Issue Nov 26, 2015 · 1 comment

Comments

Projects
None yet
5 participants
@PaulStovell
Member

PaulStovell commented Nov 26, 2015

When creating a script step in Octopus, you can paste a script into a big textarea. We're going to extend this to support choosing a NuGet package that will contain the script, and entering the name of the script within the package to invoke. This step will be able to run on the Octopus server, as well as on Tentacles/SSH machines/etc.

This would support scenarios like:

  • Deploy a database migration - the migration scripts can be in a package, with a PowerShell script that calls them
  • Deploy a reporting services project from the Octopus server
  • Deploy an Azure RM template
  • Deploy an AWS CloudFormation template
  • Regular PowerShell/ScriptCS steps that need additional files to operate

It would be similar to the standard NuGet package step, but bypasses all the conventions and "installation" of the package. We simply extract, execute the entry point script, then delete the folder.

@tothegills tothegills added the ready label Nov 27, 2015

@PaulStovell PaulStovell added in progress and removed ready labels Nov 27, 2015

@PaulStovell PaulStovell self-assigned this Nov 27, 2015

@michaelnoonan michaelnoonan added this to the 3.3.0 milestone Dec 21, 2015

@matt-richardson

This comment has been minimized.

Show comment
Hide comment
@matt-richardson

matt-richardson Jan 8, 2016

Contributor

This sounds very interesting. You could potentially also extend this to step templates, so that these can be stored in source control, packaged and published to Octopus.

Contributor

matt-richardson commented Jan 8, 2016

This sounds very interesting. You could potentially also extend this to step templates, so that these can be stored in source control, packaged and published to Octopus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment