General

  1. Fix typo in /opt/octopus/tentacle/configure-tentacle.sh

    Fix typo in /opt/octopus/tentacle/configure-tentacle.sh.
    Applications is misspelled as "appications".
    Found in tentacle-5.0.12-1.x86_64.rpm.

    read -p "Where would you like Tentacle to install appications to? ($applicationpath):" inputapplicationpath
    
    read -p "Where would you like Tentacle to install appications to? ($applicationpath):" inputapplicationpath

    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 →
  2. Use AWS IAM Roles as Octopus AWS Accounts

    When creating an Octopus AWS Account (https://octopus.com/docs/infrastructure/deployment-targets/aws) you currently need to enter an AWS Access Key and Secret Key. This means the corresponding AWS Access Key needs to be periodically rotated, creating some management overhead and potential security vulnerabilities. Rather than an AWS Access Key and Secret Key, if we were able to enter an AWS IAM Role that is assumed whenever that Octopus AWS Account is used, then we would no longer need to manage AWS Access Keys.

    In the background, Octopus Deploy would need to set it up so that the AWS IAM Role is assumed…

    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 →
  3. Go to cloned project after cloning

    After completing and saving the clone project dialog, the page reloads and your are back on the project that you just cloned from.

    To be consistent with other software I regularly use, I expect to be navigated to the project that I just created from the clone command. At the very least, I would like some sort of obvious UI with a link telling me to go to the cloned project.

    On multiple occasions, I have cloned a project and went straight into deleting custom steps and variables that aren't needed in the new project. However, I eventually find out…

    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 →
  4. Show release notes in overview

    Could you please consider showing the release notes as a hint box when user would hover the release number in the Project/Deployments/Overview view?

    Currently the release number is "clickable", so we can reach the release (and its notes) quickly, anyway there is no hint used, so it would be more comfortable just to point the cursor and read the notes.

    Thank you.

    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 →
  5. See references to projects used in 'Deploy a Release' steps

    In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.

    Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.

    9 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 →
  6. Add a view that shows all Releases across all channels and Tenants

    Please can a view be added that allows a user to see all deployments in a pipeline, spanning all tenants and channels? Having to search for these seperately causes no end of headaches as I often have to line up versions and this is made harder when they have to be searched for. Making it so they are all visible from the main page of a release as an optional view would alleviate this.

    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 →
  7. Include description field for project and library set variables similar to project template variables

    It would be helpful to have a description field for variables in a project or in library set variables. I know the idea of having 'descriptive variables' usually solves this issue but sometimes across teams it doesn't always happen.

    To save screen space it could be a descriptor you enter when making the variable then when you mouse over the variable it shows the information descriptor.

    13 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. Tentacle authentication should be able to use .pem .key.

    Tentacle authentication happens only using .pfx cert, but it should also use the .pem

    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 →
  9. "Acquire Packages" should be first step

    Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.

    Our use case:
    We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.

    Our current fix:
    Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning

    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 →
  10. Allow MarkDown files from a package to be used as manual intervention

    Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.

    I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.

    However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the 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 →
  11. 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 →
  12. Connect project to many tenants at once

    There is currently no way to associate a project to multiple tenants without going into each tenant one by one, finding the project, selecting an environment, and clicking Save. For installations with many (tens or more) tenants, this is quite inconvenient, and has resulted in hacky workarounds from third-parties.

    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 →
  13. 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 →
  14. 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 →
  15. 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. :(

    11 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  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 66 67
  • Don't see your idea?

Feedback and Knowledge Base