General

  1. Disable the 'Deploy' button whilst filters are being refreshed and affected tenants loaded

    Whilst in the deployment screen, the 'Deploy' button should be disabled whilst filters are being refreshed and affected tenants loaded.

    With the current functionality, it's very easy for a user to add a tag filter and not realise that additional tenants have been included, but are not yet visible in the 'Preview and Customize' section. The loading bar at the top of the box is subtle and easy to miss.

    Once affected tenants have been refreshed, the button should be enabled again.

    19 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 →
  2. Deployment promotion with excluded steps is not persisting chosen steps

    Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

    We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

    It would be great if you can persist the state of excluded steps to the next environments as part of same release?

    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 →
  3. Allow the visibility of what teams have access to a project/group

    Right now you can view a Team and see what project or project group that team has access to. We'd like to see the reverse as well. When we go to a project or project group we'd like to see the teams that have access along with their permissions.

    10 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. Right-click "Open link in new tab" no longer working

    This was previously asked for and done here https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/3133236-non-javascript-based-links

    But we updated from 2019.6.8 to 2019.9.10 and this has broken in at least one spot.

    If you click "Project switcher" and search for a Project the dropdown no longer gives links that can be open in a new tab.

    This makes me sad. :(

    8 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 →
  5. Support Terraform 0.12

    Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Use IAM roles instead of AWS access secrets for all external resources, e.g. feeds, targets, community library tasks

    Currently, the only way to set up AWS authentication for an ECR external feed, AWS deployment target, community library task, etc, is with an IAM user secret such as API access keypair. Our product secrutiy team has exlicitly forbidden use of secrets such as keypairs like this and requires everything to use IAM role authentication via role assumption.

    It would be lovely to replace the access key and secret key inputs with a single input for an IAM role name to assume into in order to get the needed credentials. The authentication and login could then execute on workers with…

    29 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. Support toast messages

    It would be useful to notify either all users, a team, an individual of some changes (step template to be deprecated, upgrade occuring) via a toast/message on login so that important messages related to Octopus/deployments are delivered via Octopus directly to the users that need to know.

    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 →
  8. Support inserting into an array in JSON Configuration

    Given an JSON settings file which has an array element

    e.g. { "Users": [] }

    Use Octopus variables to insert into the array rather than just replace values.

    e.g.
    define Users:0:Username = user
    define Users:0:Password = password

    Would result in the object getting inserted

    { "Users": [ { "Username: "user", "Password": "password" } ] }

    https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7

    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 →
  9. Support for High Priority Deployments/Tasks

    Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support linux-arm in Linux Tentacle

    A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.

    https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ability to copy from logs without getting timestamp interwoven

    The current implementation of Octopus Deploy makes it very difficult to copy information from the log output. The resulting copy of multiple lines includes the date information interwoven with the log data. This makes it almost impossible to copy from Octopus to create a bug in Azure DevOps.

    Attempting to copy this information results in a test block like the following:
    Failed TestPagesAreLoadingLoginPage
    December 19th 2019 08:44:12
    Info
    Error Message:
    December 19th 2019 08:44:12
    Info
    Assert.AreEqual failed. Expected:<200>. Actual:<404>.
    December 19th 2019 08:44:12
    Info
    Stack Trace:
    December 19th 2019 08:44:12
    Info
    at Platform.Specs.SystemResponsivenessSteps.ThenIShouldRecieveAMessageBackFromTheServer(Int32 p0) in H:\Agents\DEP-3_work\2\s\Platform\Outsell.Tools\TestFramework\Platform.Specs\SystemResponsivenessSteps.cs:line 137
    December 19th

    4 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. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1 3 4 5 65 66
  • Don't see your idea?

Feedback and Knowledge Base