16 results found

1. ability to add metadata to a tenant environment that shows up on overview screen

   So in our scenario we have multiple tenants and each one has 6 or more environments which are attached to the tenant. In the overview screen we see the list of tenants on the right hand column and the environments as the column header and their current version along the row. What we really need so that we don't get confused to which site we are deploying is some additional metadata on the overview screen so we can at a glance see something like what ownership of that deployment or what that deployment is for.
   
   So to explain I have tenant1, environment1, it displays V1.2.3 (timestamp) in the overview. I need somewhere there to possibly add a "?" so you could hover over and it gives you details about that specific deployment. So i could know that tenant1, environment1 is for custom deployment for customer X, managed by employee John, etc.

   So in our scenario we have multiple tenants and each one has 6 or more environments which are attached to the tenant. In the overview screen we see the list of tenants on the right hand column and the environments as the column header and their current version along the row. What we really need so that we don't get confused to which site we are deploying is some additional metadata on the overview screen so we can at a glance see something like what ownership of that deployment or what that deployment is for.
   
   So to explain I have… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Projects  ·  Edit…  ·  Delete…  ·  Admin →

2. Add confirmation prompt to quick commit

   When modifying the process of a project configured for config-as-code version control, you have the option of committing changes with a custom commit message, to a specific branch, etc. Next to that option is a "quick commit" button that commits the changes with a default commit message to the current branch.

   This quick commit option does not have any confirmation prompt associated with it, leading to the possibility of a misclick accidentally committing changes unintentionally, or with a non-descriptive message.

   It would be nice if the quick commit button had a confirmation prompt to protect against misclicks. Alternatively if there was an option to disable the quick commit button altogether (perhaps in the Version Control settings of the project) that could serve as a protection as well.

   When modifying the process of a project configured for config-as-code version control, you have the option of committing changes with a custom commit message, to a specific branch, etc. Next to that option is a "quick commit" button that commits the changes with a default commit message to the current branch.

   This quick commit option does not have any confirmation prompt associated with it, leading to the possibility of a misclick accidentally committing changes unintentionally, or with a non-descriptive message.

   It would be nice if the quick commit button had a confirmation prompt to protect against misclicks. Alternatively if there… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Projects  ·  Edit…  ·  Delete…  ·  Admin →

3. View contents of package before running step

   I'd like to see a pre-deployment preview of the contents of the package so that I know what the script path will be without having to guess the script path.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Projects  ·  Edit…  ·  Delete…  ·  Admin →

4. Allow variable set assignment through variable set

   Currently when a new variable set is created, it has to be included in projects individually. When there are many projects that should include the variable set, it would be much more convenient if the set could be included in projects via the 'usage' tab.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Projects  ·  Delete…  ·  Admin →

5. Allow variables to be set as Environment Variables

   It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.

   Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.

   If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They then function exactly like they would on the dev machine.

   This is pretty much blocking the team from moving to octopus because it is hard to debug and run efficiently and thus we are choosing to just use Teamcity for various steps.

   Note: This also means im not limited to the built in 'Accounts' that are pretty useless when it can simply support everything.

   It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.

   Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.

   If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Projects  ·  Delete…  ·  Admin →

6. Reorder variables on Project Variables Screen

   On a projects Variables screen, once we enter a new variable it stays in order on the screen. I would like the ability to drag and drop each line to a new position. This way I can ensure as I add new vars or update existing ones the ordering of them makes sense (at least to me)

   22 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Projects  ·  Delete…  ·  Admin →

7. Variable references and safe deletion/renaming of variables

   It would be nice if we could track the usage of project or global variables . They can be anywhere and there is nothing worst than having deployment time errors. Having references of the variables would allow variable renaming and safe deletion.

   27 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Projects  ·  Delete…  ·  Admin →

8. Viewable variables

   Users/groups can have edit-access to variables in 1 or more environments but it would be nice if you could give read-only-access to variables in other environments.
   I.e.: a developer has access to test and development environments but not production. It would be nice if the developer could have read-only-access to variables in the production environment

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Projects  ·  Delete…  ·  Admin →

9. Inheritable Templates

   There should be the possibility to create project templates which can be chossen when creating a new project. This should then not only copy everything, but keep the reference to the template. So when something is changed in the template, all projects based on this template should be updated as well.

   Steps coming from a template should not be editable in a subproject, but there should be the possibility to disable a specific step in a specific project.
   Also there should be the possibility to add other steps between "template steps" to customize the process.

   Teamcity has a simillar model.

   100 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   14 comments  ·  Projects  ·  Delete…  ·  Admin →
   Under Consideration  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   We have no specific work in progress at the moment, but we are actively listening in this area. Please continue to share specific scenarios.

10. Extract variables into Variable Sets

    I'd like to be able to pick a few variables and either move them to a variable set, or extract a variable set out of them.
    It's particularly useful when I want to share sensitive variables between projects.

    17 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Projects  ·  Delete…  ·  Admin →

11. Machine Variables

    I do know that this can be accomplished in other ways, however, there are some scenarios where machine variables could be useful. For example, imagine I want to set the machine's IP addresses to use in a deployment script.

    Via: http://help.octopusdeploy.com/discussions/questions/2420-machine-variables

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Delete…  ·  Admin →

12. Include Variable Libraries into other Variable Libraries

    I love the new Libraries feature. I've been using it a lot to set up connection strings and api hostnames, etc. I've started declaring variables that interpolate other variables from a different library.

    For example, let's say I have two different rabbit mq clusters, and I want to reference the hostname/username/password of one of them in a variable library for a shared component. Currently my only option is to include both libraries - the correct rabbit mq cluster library and the shared component library into a Project that needs them.

    It would be the bees knees if I could just say SharedComponentSettings (library) depends on RabbitMQClusterA (library), and only have to import SharedComponentSettings into projects that need it.

    -Aaron

    P.S. Much love from The Motley Fool

    I love the new Libraries feature. I've been using it a lot to set up connection strings and api hostnames, etc. I've started declaring variables that interpolate other variables from a different library.

    For example, let's say I have two different rabbit mq clusters, and I want to reference the hostname/username/password of one of them in a variable library for a shared component. Currently my only option is to include both libraries - the correct rabbit mq cluster library and the shared component library into a Project that needs them.

    It would be the bees knees if I could just… more

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Projects  ·  Delete…  ·  Admin →

13. Disable variables

    It should be possible to mark a variable as disabled:

    http://help.octopusdeploy.com/discussions/questions/1788-disable-variables-option

    10 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Delete…  ·  Admin →

14. User variables

    I would be nice to be able to define variables per octopus user (for example in external connections you want to store username and password for a service).

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Delete…  ·  Admin →

15. projectgroup variables or permissions on library variable sets

    Hi we would like to propose the ability to have variables at the projectgroup level or some mechanism to separate libraryvariablesets by team.

    We have multiple application teams, and some teams have projectgroups containing multiple projects that share variables. We would like to delegate the administration of these shared variables to these teams but restrict their ability to view/edit/delete those from other teams.

    The projects that are in question are not-tenanted projects so we don't have the ability to use tenant variables in this case.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Delete…  ·  Admin →

16. Promote variable to Variable Set

    If I have a variable in a project and want it to use it in a variable set, it would be nice if I could right click and promote to a variable set.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Delete…  ·  Admin →