General

  1. 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…

    22 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 →
  2. 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 →
  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. Allow 'Step Templates' to use fixed/specific package versions

    We've been trying to ensure that any 'Step Templates' created in Octopus contain scripts/code (PowerShell) that exists within a package. That package is then referenced as part of the 'Step Template'.

    The problem we have with this is that as soon as the package is pushed, it then gets used in any new releases. This means that we have no opportunity to test this in Octopus prior to new releases in pipelines using it.

    It would be useful if within the 'Step Template' we could specify/fix the package version (or specify a range) used so that all other pipeline releases…

    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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Json Configuration - Scope Target File

    Been setting up multiple pipelines for Azure Data Factory (ADF) resources, defined by a series of Json files and would like to to use the Json Configuration Variables for configuring these. In ADF you typically have a series of linked services json files, specifying e.g. connection strings, credentials, input type etc - all with the same hierarchy - E.g. the connection string would be specified as 'properties:typeProperties:connectionString' in all the linked service files - hence the problem, since all json files are applied with the same OD variables.

    I proprose an extension to the existing Json Configuration Variables feature, where…

    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 →
  11. 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.

    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 →
  12. 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.

    16 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 →
  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
    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. Allow variables to be used for Channel Version Rules

    It would be nice if the Channel Version Rules had support for Octopus variables. From a management standpoint, when you have dozens and dozens of deployment steps bound to specific Version Rules, it would make sense to be able to make centralized updates rather than going through all of the various projects, channels, and associated rules in order to make the same update.

    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. Compress the Offline Package Drop folder

    I would like it if there would be an option to compress the Package Drop folder on a target location.

    I see it is now possible to deploy it as an artifact in .Zip format.
    But i would like it if we could deploy it to a file share in .Zip format without requiring somebody to manually copy it there.
    Each Offline Package Drop folder contains a Calamari folder that is 45MB unzipped and only 10MB zipped.

    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 →
  16. 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.

    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 →
  17. 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?

    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 →
  18. Supply a list of project variables for powershell

    Currently in powershell scripts, the only list of variables is $OctopusParameters, but this list includes all the built-in Octopus parameters as well.

    It would be really nice to be able to reference only the variables defined in the current project during a deployment.

    Something like $OctopusProjectVariables

    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 →
  19. 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…

    9 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 →
  20. new user role\s

    Would it be possible to introduce a new user role\s for adding\editing\removing steps from a process?

    We would like developers to be able to add a new step but not delete or edit existing steps.

    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 →
← Previous 1 3 4 5 23 24
  • Don't see your idea?

Feedback and Knowledge Base