General

  1. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. 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 →
  11. Make deployments synchronous for a specific environment

    I help manage deployments for a software team that is working on moving from bi-weekly releases to continuous delivery. In order to transition smoothly, we have decided to have four environments in our pipeline: Dev > Alpha > Beta > Production. This allows us to continuously deliver internally from Dev (automatically deployed to from build server) to Alpha (snapshot of all projects promoted to Beta bi-weekly for staging).

    What I would like to have the ability to do is make all deployments to Dev synchronous in that they wait if there is a current deployment to Dev and stay pending…

    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. Add a step to allow deployment of a template to create Subscription level resources in Azure

    Azure allows for the deployment of Subscription level resources via a template, but currently there is no out of the box step to do this in Octopus.

    https://docs.microsoft.com/en-us/azure/azure-resource-manager/deploy-to-subscription

    It would be great if we could have a built in step, along the same lines as the 'Deploy an Azure Resource Manager' template step.

    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 →
  13. Enable worker pool support for 'Deploy a Package' step

    We have nearly a dozen client/WPF projects that primarily consist of backing up a directory and then overwriting it with an updated package (size ranging from 20-350MB). Each of these projects push their packages to 20 remote servers, but the servers cannot host tentacles due to our security policies, so we run the steps from one of our Octopus hosts (via tentacle installed alongside the manager service). This is slow and expensive on the Octopus host, especially when there are many other deploys underway. Worst of all, it forces steps to deploy in serial versus parallel because all steps are…

    11 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. Install Let's Encrypt module on Octopus Cloud to enable a CNAME for ODC instances

    With Octopus Cloud 2012.5.9 we can’t assign our own CNAME to the server instance due to the Let’s Encrypt module being missing.

    It is ok for internal use, but if we want Tenants to have access to see what we’ve deployed for them, then we would want to use octopus.mycompany.com not mycompany123.octopus.app.

    It might seem minor, but does Octopus use octopus123@yahoo.com as your public email address for customers? Nope, and we don’t want to either :-)

    Please add back the excellent Let’s Encrypt module in Octopus Cloud and route port 80 or just .well-known/acme-challenge/ to the relevant instance. Octopus Cloud…

    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 →
  15. Allow the removal of the date filter from the audit display

    I can understand for performance reasons wanting to restrict the audit form, but it's incredibly frustrating to use the existing interface to find the creation date of an object when the date filter refuses to go away, and in fact seems to want to shrink to 1 month when wrestled with.

    I'm willing to wait a few seconds for the information I want. Just show it to me.

    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. chained deployment to specific targets

    If you deploy to specific targets in an environment but one the steps triggers a chained deployment, the chained deployment will target all hosts in the environment. It would be better if the chained deployment continued to target only the specific hosts that were originally chosen.

    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/write a file to a location

    Sometimes we just want to write out a simple file to disk. For example writing out a basic text file to a location. While you could have a basic template in an repo sometimes you want to write out a straight file to disk with the normal support for variable substitution. Example, write a file to a queue or change a basic configuration file.

    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 →
  18. Allow specifying Machine Policy for machine in Azure Resource Manager Template extension

    Specifying Policy for a machine in a new Tentacle through the Azure Extension Agent would be valuable.

    In our scenario we use ARM templates for new infra structure as code for "cattle". The extension allows for dynamic creation of short-lived environments in Development.

    However, we want to utilize the Octo automatic de-registration of agents as dev infra is removed via Machine Policy. (Machines in Octo disappear when automatically after a developer is done with a VM.)

    Having the "Policy" as a parameter to the extension would allow this to be setup easily one time instead of a post-build step manually…

    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. have a better way of handling parameters in arm templates

    When setting up a new ARM template for use in octopus we set the default value of all parameters to #{something} so that the 'parameter' page in octopus is auto populated.This works great for most values but if we have a secure string octopus will update the 'default value' in the arm which will show up in the deploy history in Azure. We would like to see some way to handle this so we can ignore updating the default value or auto-populate the parameters page without needing the default value or some other way to handle this a bit cleaner.

    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. Support Azure Service Fabric Mesh

    The Service Fabric Mesh deployment model is in public preview since a couple of months back and GA is expected this spring. Being mainly ARM template and container based, the SF Mesh deployment is probably possible to accompish by custom scripts today, but good out of the box support in OD would be very valuable.

    13 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