General

  1. Release created date (system variable)

    The system variable Octopus.Deployment.Created is updated/changes between deployment to the different environments, but it would be great to have a static value for when the Release itself was created.
    So i suggest a new system variable Octopus.Release.Created that says when the release was created (with the Create Release button).

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Assign Worker Pool(s) to Environment(s)

    Rather than using cloud regions it would be much easier to assign a worker pool(s) to environment(s). We have a lot of security requirements and being able to use specific workers per environment would help us tremendously.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Deployment Steps - Loop Step with variable

    Hi,
    I have a service/container and I want to launch it in the same machine a number of times (variable to be applied per environment/tenant) .

    Do you have something for this? Can you put this?

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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…

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. I have multiple nuget packages that I want to deploy to a single location, can this be done with Octopus Deploy?

    I have multiple nuget packages that I want to deploy to a single location (these nuget packages all make up the single Application), can this be done with Octopus Deploy?

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Show the Project name on HTML Title instead of "Overview - Octopus Deploy"

    When you navigate to a project, you get to the Overview page as a start. When you open up many projects at once (cause a change triggered multiple CI for example, which should be deployed) all of them will show "Overview - Octopus Deploy" in the HTML title and as such it's also what's displayed on the browser tabs:

    You loose the ability to distinguish between these tabs. It also means that if you bookmark multiple projects then you'll have to change their title manually to have a valuable label for them. You have to click around them to figure…

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Deploy Release step should prevent picking releases from a different lifecycle

    When creating a deployment 'parent' that utilizes the "Deploy A Release" step 'child', it's possible to create a 'parent' release with a 'child' release version that uses a different lifecycle. When attempting to deploy, the following cryptic error is returned:

    The step failed: Activity <Child Step Name> on the Octopus Server failed with error 'The release has unresolved defects and cannot be deployed to this environment.
    Once you have corrected these problems you can try again.
    If the problem is related to a variable you will need to update the variables for this release or recreate the release for the…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow linking of the Enabled checkbox to a variable

    For various steps it would be nice to allow the "Enabled" checkbox to be linked to a variable. For example in the "Deploy to IIS" step template.

    This would work just like it does in the website bindings popup, each binding can be linked to a variable.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Scheduled deployments allow select release versions

    Hi,
    We would like to select certain release versions in the scheduled deployment triggers similar to how we create a new release and can select a release version
    Currently it doesn't seem to be possible and it uses only the latest release
    Hope this can added in the next Octopus release
    Thanks,
    KK

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  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

    We're glad you're here

    Please sign in to leave feedback

    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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Deployment of more than one certificate in one step

    We need to put multiple certificates into the trusted people-store, and number of certificates must be configurable in one step.

    Tried putting multiple certificates into the same scope for a variable, that only published the first one.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add "Request Deploy" button

    It would be nice if a deploy could be requested when you don't have permissions. For example our Acceptance and Production environments can only be deployed to by the Release Management team, so it would be nice to be able to Request a deploy from within Octopus for a certain release version.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    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