General

  1. indicate if a release had skipped process steps

    we want to quickly identify if a release had skipped process steps.

    Some kind of icon or status color.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Decorate overridden config file settings with an Octopus tag (or something)

    Some of our services have large config files and we will allow some settings to be defaulted (not configured through the Octopus UI) and others must be configured. I would like a Project Level setting to be included that if enabled would decorate the deployed config file with some indication that Octopus overrode the setting. This would help tremendously to be sure which settings were defaulted and which were set by Octopus.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow configuration transforms on any XML file

    Currently configuration transformation only works with files with the extension .config.
    As XDT works with XML it would be great to be able to apply transformation on any XML file. For example on .dtsConfig for SSIS packages.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow option to set or override variable values from within a Manual Intervention step

    While we make great of environments and machine roles for our production servers and devices, we still find it difficult to manage certain test scenarios without having to maintain a very large collection of test environments in order to mimic each distinct production environment. It would be nice to have an option, at the deploy time, to override or set certain variables, allowing a single test environment that can be dynamically configured to use various settings.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add support for msdeploy package-style parameters transformations

    This discussion started as a support thread here:

    http://help.octopusdeploy.com/discussions/questions/2571-web-package-based-parameters

    Let's say I have an App.config for a Windows Service that looks like this:

    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
    <!-- snip -->
    <system.net>
    <mailSettings>
    <smtp from="user@localdomain.org">
    <network host="smtp.local" />
    </smtp>
    </mailSettings>
    </system.net>
    <!-- snip -->
    </configuration>

    With the built-in transformations (appSettings and connectionStrings) I cannot replace the SMTP server host.

    For web projects in the past, I've used msdeploy (or web deploy) package parameters to do this transformation from environment to environment.

    The idea is you create a parameters.xml file locally to your project, and then each environment has a…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add ability to specify a minimum powershell version for a step template

    Step template should not run if minimum power shell version is not met.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Variables in NuGet package ID per enviroment

    It would be great if the NuGet package ID could contain a variable that was resolved on a per environment basis instead of only once when the deployment is created.

    We have the same process for each client with a different installer and out current solution has been to package them all into single NuGet package and then grab the correct one on a per environment basis with a powershell step.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Enable a failure/success variable to be used in the email subject

    We would like to create one step template that will send an email to the developers with the deploy result.
    It would be nice to have a variable like Octopus.Deployment.Result to include the deploy result in the Email subject.
    As far as I can see you can not use powershell or the if structures from the Email body?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support ZIP(compression) of files/folders

    Most of our deployments begin by first copying existing deployed files/code to another folder as a backup. This is required in case a quick rollback is required.

    Would be nice if I could zip those files to save disk space.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow Octo.exe create-release command line to specify an alternative NuGet feed than the one(s) indicated on the steps of a project.

    Allow Octo.exe create-release command line to specify an alternative NuGet feed than the one(s) indicated on the steps of a project.

    We have a DEV feed which is used for all development builds and development deployments. Due to circumstance beyond our control, we cannot have our development environment match all other environments close enough to want to promote releases from development.

    We have a MAIN feed that is for all other environments (QA, TRAIN, PROD).

    The problem we have is that a deployment step is tied to a specific NuGet feed. This means having to maintain two versions of a…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Deploy without storing a package or release

    I want to use Octopus to deploy an application without having to store a nuget package or create a release for it. The reason for this is that some of my automated tests are end to end tests that I run against a deployment in my WiP environment. If these tests fail, I don't ever want to be able to deploy that version of the application. The best was I see to do this is to be able to directly deploy a package through Octodeploy. Once these pass I could potentially create a release from what I just pushed or…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Include Variable Libraries into other Variable Libraries

    I love the new Libraries feature. I've been using it a lot to set up connection strings and api hostnames, etc. I've started declaring variables that interpolate other variables from a different library.

    For example, let's say I have two different rabbit mq clusters, and I want to reference the hostname/username/password of one of them in a variable library for a shared component. Currently my only option is to include both libraries - the correct rabbit mq cluster library and the shared component library into a Project that needs them.

    It would be the *bees knees* if I could just…

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Make OctoPack an developmentDependency

    OctoPack is a build time tool not a project dependency.
    Adding the developmentDependency attribute will allow other tooling understand this.

    see http://nuget.codeplex.com/workitem/1956 for more info on developmentDependency attribute.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add the option to disregard pre-release packages when creating a release by default

    I noticed that when creating a release pre release packages show up in the latest column when their version number is the highest available.

    Pre-Release version are usually used for (feature)branches, hotfixes or alpha/beta version of new major releases. All things that deviate from the regular release flow.
    I would prefer having to pick the special version using the specific version picker and only see the latest non pre-release version
    in the "latest" column on the "create release" page.

    A simple checkbox to turn that feature on/off on the projects's settings page would do. That way you could set it…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add support for a tool library

    Currently when we need some tools (sqlpackage.exe, sqlcmd.exe, some DLL...) to be present on the tentacle for our deployment script we create a NuGet package with the tool and have to manually add a Deploy Package step for each tool to deploy it in a standard path so we can then use them from PowerShell scripts/

    It would be great to have a tool library:
    - we create a tool by specifying a NuGet package, a name and a description
    - in each steps (template steps or process steps) we can specify which tools is needed
    - when deploying the…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enable the user to define a default release behaviour for each step in a project

    When creating a release the user is given three options to configure a package version for each step, Latest, Last, Specifc. The default is Lastest.

    Allow the user to specify the package version default behaviour in each step.

    The user could then ensure a package stays at a particular version without having to set the version each time they create a release.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Create a step template that applies config transformations

    Have an entry field that accepts the same sort of content as is seen in the transform window here: https://webconfigtransformationtester.apphb.com
    as well as maybe a file pattern/name to match the transformation to.

    This way one can avoid building multiple instances of an application, one for each build configuration (environment), transforms don't happen at build time and can take place as part of a deployment.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Enable one to be able to iterate a list of last installed directory paths for steps in project

    Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add a Manual Intervention Counter Sign feature

    It would be nice if when adding a manual intervention step I could select an 'Anyone but Deployer ' option that would mean that anyone except the person doing the deployment could approve a deployment.

    It might also be cool to have a generate captcha option, so that the user has to fill in a google captcha before they can approve the continuation of the deployment.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Display just the variables applied to a release on the release's page

    The Variables section a Release page appears to show all variable that apply to the release, would it be possible for any variables which are obviously being overwritten to be omitted from this list?

    As an example, if I have a variable in a Library which is being overwritten by this particular project, at the moment both will appear in this list.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base