Settings and activity

NuGet is introducing signed packages: https://github.com/NuGet/Home/wiki/Author-Package-Signing

@Christian There are some downstream issues with being able to extract packages on the tentacle/SSH side. Our extensible model does not (yet) reach that side of the system.

What if we added the ability to add a plugin for a particular feed type (eg NPM, Artifactory) and the plug in returned a Zip compatible file (repacking it if the original is not).

Is there anything in these package formats that would be useful after it is retrieved from the feed?

We deploy a lot of packages, so when we create a new release it often becomes a pain to click "Last" on each package individually, in case we need to deploy last (not latest) versions of them.

In 3.5 we have implemented both Azure AD and GoogleApps Auth. Both support 2FA and have been mentioned in the comments of this suggestion.
We realize this is not Octopus supporting 2FA (only that these services also have 2FA as a feature) so we will not close this suggestion as completed.
However, if those above solutions are what you were looking for and why you voted, please remove your votes from this suggestion so we have an idea of the need that is still out there.
3.5 also added extensibility for authentication (all OSS), so if there is a great need, and you have the means and expertise we would absolutely review your PR :)

original request: http://help.octopusdeploy.com/discussions/problems/48779

Have you seen the re-order steps button that allows you to change the order of steps as they appear in the project process?

Or are you referring to another area of the product?

Hi Tim, Yes, this should be possible.

The powershell we use to install and configure Octopus for an Azure marketplace VM is available at https://github.com/OctopusDeploy/azure-marketplace, so you could use that for inspiration.

If that doesn't help, can you drop me an email to support(at)octopus.com and I can see if I can assist.

Cheers,
Matt

The settings mentioned so far are:

- Pipeline Mode (Integrated or Classic)
- Number of Worker Processes
- Recycle configuration

Are there any other requests?

We have created a GitHub Issue to follow and get involved with the design of this feature: https://github.com/OctopusDeploy/Issues/issues/2755

This behaviour could perhaps be achieved using the new Multi-Tenancy feature provided in Octopus Deploy 3.4 (http://docs.octopusdeploy.com/display/OD/Multi-tenant+deployments)

In this scenario you can create a seperate Tenant for each of your hotfix builds, which specific machines scoped to each Tenant. Using Channels also scoped to each Tenant, you can then create and deploy releases with confidence that specific builds, as defined by the version range or tag information, only go to specific machines. In this approach you can keep your list of environments to a minimum.

Using tenants and scoping machines to tenants, means that only deployments for that tenant will be able to go to that machine.

Is there anything with this approach that you think wouldn't achieve the goals proposed by this suggestion?