General

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.
You can remove your votes from an open idea you support.
To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Better guidance for TFS users

Provide some really good guidance to help people use TFS and Octopus together.
114 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
4 comments · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminPaul Stovell (Founder, Octopus Deploy) responded

We’ll be building this very soon
Allow non-tenant and multi-tenant deployments to the same environment

The new 3.4 Multi-tenancy feature is great. But there is a limitation preventing it for some to use it effectively.

We have several projects, some have multi-tenant deployments (per client) some others not (tool project, shared services projects etc).

We deploy all these projects to the same test and staging servers and some as well to production environment. Meaning, the same machine might be used for multi-tenant and non-tenant deployments.

The current 3.4 release does not allow us to use the same environment/target for both type of projects.

Workaround as published (setup dummy tenant instance) is a less desirable, as we would need to reconfigure too many projects to use the dummy-tenant; Next to that it also sort of makes history and promotion of releases over environments less nice (redo releases using this dummy-instance just to be able to promote the correct instance up.

Workaround is definitely possible, but a nice fix (just allow mixed types of tenant-non-tenant projects to the same environment by configuration is preferable.

The new 3.4 Multi-tenancy feature is great. But there is a limitation preventing it for some to use it effectively.

We have several projects, some have multi-tenant deployments (per client) some others not (tool project, shared services projects etc).

We deploy all these projects to the same test and staging servers and some as well to production environment. Meaning, the same machine might be used for multi-tenant and non-tenant deployments.

The current 3.4 release does not allow us to use the same environment/target for both type of projects.

Workaround as published (setup dummy tenant instance) is a less desirable, as…
88 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
1 comment · Deployment features · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminOctopus Developer (Admin, Octopus Deploy) responded

We have planned this work as mentioned in a comment! https://github.com/OctopusDeploy/Issues/issues/2722
Parallel deploy throttle

Currently you can throttle the number of package aquisitions and the number of machines which will run steps in parallel.

We see issues whereby too many steps run on the same machine causing out of memory issues.

Can you please add configuration to limit the number of steps running in parallel on a single machine
13 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
1 comment · Deployment features · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminOctopus Developer (Admin, Octopus Deploy) responded

Good news – we’ve started planning this work over here: https://github.com/OctopusDeploy/Issues/issues/3305 :)
Hide the "un-tenanted" release goup

It would be nice to hide the "un-tenanted" group of releases shown on the dashboard and project overview, if the project is configured as "require a tenant for all deployments". We don't want to delete these old releases, but they are no longer relevant to us and interfer with the information shown on the dashboard.
4 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
4 comments · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminOctopus Developer (Admin, Octopus Deploy) responded

See https://github.com/OctopusDeploy/Issues/issues/3169 for our plan and a workaround to get you started right now!
Allow people to write plug-ins/add-ons with an SDK

Potentially create some kind of SDK to allow for hooking into various parts of Octopus. e.g.: permissions/users could be given a custom implementation and provided by active directory.

~~~~~~~~
Example plugins we should build:

https://github.com/OctopusDeploy/Issues/issues/511
https://github.com/OctopusDeploy/Issues/issues/312
56 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
14 comments · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminPaul Stovell (Founder, Octopus Deploy) responded

We’re going to start on this very soon. I’d love to collect more examples of what people want to do with plugins (not so much how the plugin would work/what kind of extensibility, but the actual problem you want to solve)
Machine policies cleanup unavailable machines days or hours?

User interface shows hours and minutes, however the API is returning a time span of days, so for example I've set 99 hours, but the time span from the API is 2376 hours or 99 days.
16 votes
Vote

Sign in
prestine

Your name

Your email address
Check!

invalid email

(thinking…)

Reset

or sign in with

UserVoice password

Forgot password?

Create a password

I agree to the terms of service

Signed in as (Sign out)

Close

Close

You have left! (?) (thinking…)
1 comment · Deployment features · Flag idea as inappropriate… · Delete… · Admin →

planned · AdminVanessa Love (Admin, Octopus Deploy) responded

This has been confirmed as a bug so has been moved to GitHub. Thanks for the report. Please reach us on our support channels to inquire or report bugs like this :)
https://github.com/OctopusDeploy/Issues/issues/2938