Allow specific package version to be selected for "script file inside a package" step templates

rmy's Avatar


19 Oct, 2017 11:26 AM

We are using the "script file inside a package" functionality for some of our custom step templates, since it allows us to have the code under source control and with a full build/test/deploy pipeline, which is great.

One limitation though, is that if I make a change and push the package containing new step functionality to Octopus nuget feed, all new releases that use the step will pick up the newest version of the package. I would like to see the option to tie the step to a specific version of the nuget package, so that projects can control when their releases will include the package containing the new step implementation (by updating the step).

So to make the new step implementation available, we would need to update the package version on the step definition, then I could test the new functionality without affecting other projects.

Make sense?

  1. Support Staff 1 Posted by John Simons on 20 Oct, 2017 12:36 AM

    John Simons's Avatar


    You should be able to control the version of the script package as part of creating a release.
    See attached screenshot.

    Hope this helps!

  2. 2 Posted by rmy on 20 Oct, 2017 11:03 AM

    rmy's Avatar

    Does not really help, the developer creating the release will not know to choose anything other than the default, which would typically be the latest version. I want us in DevOps to have control over which version they use.

    The actual scenario is that I have refactored the step template logic in my package, and I wanted to test it in a real deployment before I release it to my customers.

    I guess there are other (perhaps better) ways of achieving this, I should probably consider some sort of canary release process in future.

    Venlig hilsen

    Richard Lloyd Money
    Application Lifecycle Management Specialist

    En god ven af huset - se mere på<>

    [cid:[email blocked]]
    [cid:[email blocked]]

    [cid:[email blocked]]<>

    BRFkredit sender e-mails og vedhæftede dokumenter i ikke-krypteret form. Hvis du ikke ønsker at modtage oplysninger fra BRFkredit pr. e-mail, beder vi dig meddele os det via brev eller e-mail. Denne e-mail kan indeholde fortrolig information. Hvis du modtager e-mailen ved en fejl, beder vi dig informere os om det hurtigst muligt. Samtidig beder vi dig slette e-mailen uden at videresende eller kopiere indholdet.

    Fra: John Simons [mailto:[email blocked]]
    Sendt: 20. oktober 2017 02:37
    Til: Richard Money
    Emne: Re: Allow specific package version to be selected for "script file inside a package" step templates [Questions #14154]

  3. Support Staff 3 Posted by John Simons on 23 Oct, 2017 01:04 AM

    John Simons's Avatar


    Maybe a special beta feed that you control and then update the step template.
    Or the other option is to have these scripts inline in the step template so that you can control the version updates per project, see


  4. 4 Posted by kirru4all on 08 Dec, 2017 12:40 AM

    kirru4all's Avatar


    Is there any script to compare the release version with Nuget version? When I am deploying to an environment, it actually picks different nuget version than the one which we want to.


  5. Support Staff 5 Posted by John Simons on 13 Dec, 2017 04:26 AM

    John Simons's Avatar

    Hi Sahith,

    Can you send us some screenshots of exactly what you mean ?
    Also, there is no correlation between the nuget package versions and release version.


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac