General

  1. Use Python Virtual Environment instead of root Python

    Using a virtual environment would be much more secure, and it would potentially give the opportunity for admins to modify the environment without changing the configuration on the servers directly.
    Also, it would give Octopus the ability to package Python as part of Calamari rather than the admins having to install Python on all the Tentacle servers.

    1 vote
    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 →
  2. Support Python's 'logging' module rather than 'print*'

    Support python’s built-in ‘logging’ module rather than ‘print’. it’s very easy to use and supports different log levels out of the box, and logs to stdout by default. I am getting “name not defined” errors using the ‘printverbose’ command when I try to edit scripts outside Octopus.

    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 →
  3. Output more info alongside NativeCommandError

    Rather than throwing a standard PowerShell error stack (which is only helpful in a PowerShell script), there should be some kind of log output from the Calamari that gives an indication as to what the error is (in the case of Python, a full stack trace would be nice).
    NativeCommandError's are almost always unhelpful because the output is always truncated after `"${env:TentacleHome}\Calamari\[version]\Calamari.exe" run-script`

    1 vote
    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 →
  4. hide/retire/disable step template

    It would be great to be able to hide/retire/disable step templates from the Installed Step Templates view, so that our user would not be able to add the specific step anymore.

    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. Import variables from .config file on project setup / first run

    When setting up a project for the first time, I manually copy and paste variables from config files (appSettings and connectionStrings) and it would be useful if I could have them imported and set to the value from the config during setup or on first deployment to QA / first environment. Given a large number of variables, this will be where most time is spent during project setup.

    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 →
  6. Notes for Project Variables

    Have another column for the project variables for notes/documentation. This would allow for information about what the variable is for, possible lists of valid choices, what those settings do. Most are self explanatory, but some do need additional documentation and it is better than keeping this info in a separate location.

    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 →
  7. Increase the density of the dashboard

    The Dashboard somehow manages to show only 8 of my projects on a full-screen 1920x1080 browser. There is really no reason it shouldn't be able to show more than twice as many. There is just so much whitespace. This app should be about utility, and scrolling/searching really reduces the utility here.

    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 →
  8. Handle network card changes differntly

    We had an issue where Azure changes out our network card which caused octopus to hang waiting for the interface to come back online as if the cable was just unplugged. As the interface was changed this meant the service hung until it was restarted. We would like to see octopus handle this better / perhaps crash out when the network goes away for a longer bit of time so that the service can restart on its own and pick up the new network.

    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 →
  9. Performing dry run with octo.exe push (--whatif)

    Looking at the documentation for “octo.exe push” (https://octopus.com/docs/api-and-integration/octo.exe-command-line/push), but I cannot see any option to perform a dry run. The ‘create-release’ command has a ‘whatif’ param, and it would be really handy to have this on the ‘push’ command as well.

    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 →
  10. 1 vote
    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 →
  11. Create a Build Information step for GitLab

    We would like to include build information (commits) from GitLab into our packages so that we can automate the release notes creation from packages.

    The https://octopus.com/docs/packaging-applications/build-servers#build-information page states that "The recommended way to supply the build information is to add the Build Information step" but there is no GitLab step.

    1 vote
    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 →
  12. Create a point in time restore out of the audit logs

    Add a button on the audit log screen to restore deleted items. I am specifically looking for the ability to restore deleted process steps or other unintended changes to the configuration.

    4 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 →
  13. Have Tenant name fully display on Infrastructure page without hovering

    It would be helpful if you could have the Tenant name display on the Infrastructure page under Deployment Targets instead of hovering.

    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. Include unhealthy tentacles in the Deploy Release screen

    On the Deploy Release screen, if you have multiple Tenants selected, you see, per Tenant, if there are any “Unavailable” Tentacles for that tenant. We would like it to also show how many “Unhealthy” Tentacles there are, ideally as a separate, less severe (yellow?) classification.

    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 →
  15. Click on role in process to show related machines

    I am aware that it is possible to filter targets by role in the Infrastructure UI. However, my usual workflow is to notice a role in a deployment process of a project and then try to look for that role.

    Currently, this means copying the role name, going to Infrastructure and pasting the role there.

    My request: Allow the role labels on deployment steps to be clicked in order to open a new tab at the "infrastructure/machines?roles=<clicked role>" URL.

    Should be super simple to implement and significantly reduce the amount of clicks needed in this scenario (which is very frequent,…

    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 →
  16. Create a server version of Octopus Deploy for JIRA

    The Octopus Deploy for JIRA plugin (currently Cloud only) is a nice feature, but a lot of companies use on-prem versions of JIRA. It would be nice to have a server version of the plugin that can be installed so we can properly integrate Octopus Deploy and JIRA, especially for the capturing and tracking release notes.

    1 vote
    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 →
  17. Integrate Octopus with ServiceNow

    the ability to integrate ServiceNow form approve or change approve to trigger octopus deploy

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. A project should have a unique identifier

    We run automation on our projects and found that each project does not have a unique identifier. The slug should be unique but we've found that when the project name has been renamed, the slug changes as well.

    It would be nice to have some unique id that cannot be changed.

    1 vote
    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 →
  19. Support SemVer 2.0.0 for Channel Version Range, with regex to match build metadata

    Semver 2.0.0 support has been added to Octopus, now supporting both pre-release tags and build metadata, e.g.

    2.0.0-pre.release+build.info

    However Channel Version Range matching has not been expanded to also support SemVer 2.0.0, and still only allow matching on SemVer 1.0.0 components, the version number (range) and pre-release tag (regex).

    I suggest you add SemVer 2.0.0 support to Channel Version Ranges, adding a second regex to optionally match on build info.

    The will enable users to automatically select and restrict the correct deployment Channel for the type of build.

    Use case 1: We have some projects that use opinionated frameworks that…

    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 →
  20. Upload of environment variables from .env

    I think it would be nice to have this feature on Octopus.
    So I was given a deployment task and I had multiple environment variables to upload.
    I am the lazy type so instead, I wrote a python script to enable me to upload all at once in just a sec.

    I hope this saves someone too

    https://github.com/opemipoVRB/Python-Octopus-Client

    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 →
  • Don't see your idea?

Feedback and Knowledge Base