General

  1. Retention policies on offline targets (artifacts)

    Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle

    15 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 →
  2. Encrypt variables using Certificate

    Add the ability to encrypt variable strings using something similar to the variable filters.

    Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}

    6 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 →
  3. Service fabric client application credential authentication (Azure AD)

    User credentials are the only supported method of authentication with Service Fabric and AAD. Client application credentials are not yet supported. It would be great to use the actual AAD Application to authenticate.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Improve "Substitute Variables in Files" help text for "Run a Script"

    When you configure a "Run a Script" deployment step, you can reference a package, and add the "Substitute Variables in Files" feature. Within the help text it says "A newline-separated list of file names to transform, relative to the package contents." which is inaccurate:

    For me, using a simple, relative path here e.g. "index.html" didn't work. I needed to use the full extracted path of the package e.g:

    {Octopus.Action.Package[EdibleCode.Something].ExtractedPath}\index.html

    Also, you can reference multiple packages for a a run a script template, in which case "relative to the package contents" doesn't make sense and needs clarifying.

    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. Export Audit as JSON

    When I use the Export function in Audit, the Details column is a mix of HTML and JSON.
    For example:

    <span>{<br> "Id": "variableset-LibraryVariableSets-76",<br> "OwnerId": "LibraryVariableSets-76",<br> "Version": 11</span><del style="background:#ffe6e6;">5</del><ins style="background:#e6ffe6;">6</ins><span><br>}</span>

    I understand that this is a way to show what the changes were, but this format is only usable for display in HTML, not for parsing the exported audit via any tools.
    Would it be possible to export this as JSON and indicate the change in some other, structural way?
    E.g.

    { "Id": "variableset-LibraryVariableSets-76", "OwnerId": "LibraryVariableSets-76", "Version": { "OldValue": 115, "NewValue": 116 } }

    Or in any other way which would…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Disable Chrome AutoFill on inputs

    The chrome autofill gets in the way of dropdowns/multi-selects. There is not the ability for a user to disable autofill for specific websites, but this is supposed to work on the developer side:

    https://stackoverflow.com/questions/40200130/how-to-disable-chrome-to-autofill-username-email-password/40200269#40200269

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Sort pipe for #each iterations

    When iterating through a collection variable using #{each var in array}, it would be helpful to have a sort by pipe
    Eg: #{each var in array | orderby var.property}

    2 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 →
  8. Document Octopus Package metadata Json file format

    The octo.exe push-metadata allows to provide package build information, but its format is not documented.

    The documentation available at https://octopus.com/docs/octopus-rest-api/octo.exe-command-line/push-metadata states that the "metadata-file" parameter should be a "Octopus Package metadata Json file".

    What is the format expected for that "Octopus Package metadata Json file" ?

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Trigger Deployment Through Azure Function

    Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.

    This solution would allow for various creative integrations within Azure.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Release Versioning by Channel

    Right now defining the Release Versioning approach happens at the Project level. When there are multiple channels, it would be nice to instead define them at the Channel level. In the case where you may be deploying 2020.1.0 and 2020.2.0 releases to different environments, if you change channels you have to go change the Release Version at that time as well. Then if you have automatic releases setup it will increment against an incorrect version.

    Example:
    "Test" channel limits to 2020.2.0 packages. Create an Octo Release 2020.2.0.1 and release.

    Then create a release for a "HotFix" channel which limits to…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. On Task Summary of a Release Deployment, show an indicator if the package was not deployed because it was already on the deployment target

    When steps are executed, right now it will show a green check if success or a red x when a step fails. It would find it helpful to know which steps actually deployed a new package to a deployment target vs. those that didn't do anything because the package was already deployed to the target. This could just be another type of indicator. Right now it just shows success whether it deployed a package or if it already existed. You have to drill and review the logs to determine which path happened.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. On Create Release, highlight Steps that have a different "latest" package than "last"package

    It would be nice to visually see the Steps that will be deploying a different package than the last one that was in a release. This could be done by just highlighting the row in a different color.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow Commit Comment when Saving Project

    On the face of it, a simple request... add am optional commit comment when saving an edited project. When going through the audit looking at project changes, it would be nice to simply read a project change commit message, when deciphering bit of JSON. It would be optional, so the JSON change is still available.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow Variables to be Version Controlled

    Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

    I would like to be able to version octopus variables, this would include:
    - Who
    - When
    - When deployed
    - The ability to roll back/forward.

    At the moment we have to source control much of this type…

    150 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide the ability to generate cryptographic strong passwords

    When deploying application containers, there can be times when you want a password that no human needs to know and survives only for the lifetime of the container.

    Our primary use case is generating secure keystores for certificates, etc. At container start-up, it will generate a new local keystore and we then have the ability to dynamically sign CSRs generated within the container via an external signing service.

    We do not want to leave the keystore nor the certificate objects without any password, but also do not want to store the values anywhere external to the container.

    Granted, we certainly…

    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 →
  16. Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button

    Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button. This is the same thing that Octopus already has for variables. Just do it for Processes!

    Nothing worse than having to make a small powershell script change then create a new release and run it back up the runway or having to temporarily manipulate the lifecycle to get it re-deployed to where you want it to go with the updated process.

    I want to be able to go to the release. Hit update processes for that release to what I just changed on any process then be able…

    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 →
  17. Export Variables to JSON Should Be Same Order As UI

    Given the Octopus Projects are not source controlled, comparing projects is quite difficult, so I resort to Export process and export variables to json and then do a file compare.

    This is made difficult when comparing variables, as the json file is in no particular order. It seems the most recently edited variable is at the bottom.

    Can we please arrange the variable in a set order, perhaps the same as the UI.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Separate permissions in the User Role "Project Contributor"

    Currently, in order to allow developers to access and edit variables, they are also able to edit process steps including disabling them. This means that they are able to disable audit steps before deploying.

    If process edit was a separate permission we could split out the ability to edit variables and the ability to edit/change process steps

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  19. "Use the version number from an included package" plus incremental number

    "Use the version number from an included package" isn't as useful as it could be because whenever I modify a deployment process and go to create a new release, Octopus complains the release version already exists. So I either have to delete the old release or append ".i" to the version number. I would estimate I've appended ".i" about ten thousand times over the years. Would be nice to not have to do this.

    Basically this:
    https://help.octopus.com/t/how-to-create-a-release-version-with-package-number-and-an-incremental-number-with-it/23869

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support the creation of images as a task using packer

    Packer is a versatile tool, especially when working in a multi-cloud environment. It can be used for both creating both base gold images that can then be fully built on later or fully built imputable images.

    I see an octopus step being able to be used to:
    1) create or pull (from a repository) & update a json template with variables & transformation.
    2) next packer validate
    3) packer builds the image.

    ideally, there would also be an "Octopus" provisioner for packer that would allow the download of repos, call templates, transforms, variables install tenticle via cli

    but even it…

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

Feedback and Knowledge Base