522 results found
-
Use nuget dependencies to track dependency between projects in a given environment
I have read the section on not using dependencies (http://docs.octopusdeploy.com/display/OD/Packaging+applications) and I agree but I think we're missing a nice feature if we consider dependencies as being releases done by Octopus to a given environment that include the nuget that is defined as a dependency. Consider this:
MyOrg.MyApp.Web 1.0.0.0 depends on MyOrg.MyServiceApp.RestApi 1.5.0.0...2.0.0.0.
When I deploy MyOrg.MyApp.Web to environment Production Orcopus could check if I have a release in that environment that deuccessfuly deployed MyOrg.MyServiceApp.RestApi 1.5.0.0...2.0.0.0. Essentially this would make sure all my dependencies between projects are deployed within a given environment.
It could also warn me about…18 votes -
Allow integer and boolean types in JSON Configuration Variables Feature
JSON Configuration Variables Feature only support string substitution at this time. At least integer and boolean type should be supported as well.
17 votes -
Allow configuration transforms for JSON files
Currently the Configuration Transforms runs configuration file transforms on XML formatted config files.
It would be useful to enable config transforms on JSON files as well, e.g. an appsettings.json file.
16 votes -
Add ability to loop a deploy step where multiple roles and role scoped variables are present
Have a scenario where I need to deploy the same package multiple times on the same set of servers under different custom directories and different IIS web applications. There are role scoped variables which get picked up for custom installation directory and also appsettings.
I understand that the documentation under https://octopus.com/docs/key-concepts/machine-roles clearly states:
"This means that the step will only execute on Tentacles with at least one of those roles. This does not mean that if the step is scoped to multiple roles that it will run for each role. Instead it will run that step for all machines that…
16 votes -
Better view of un-tenanted deployments
Currently when I add tenants to the project an overview is changing. Without tenats I see deployment for al channels. After adding even one tenant overview changes so I see un-tenanted deployments as single bar. And I see no option to see previous overview which were very helpful. We are working with feature branches with a lot of different channels and now it is hard to check which version is on which environment. It will be great if I can see old overview after clicking "un-tenanted" icon.
16 votes -
Manual intervention approval to apply for multiple tenant deployments
If you have multiple tenants that you deploy to, and each deployment has a manual intervention step, you have to approve each one individually. As this can become very cumbersome, it'd be a great improvement to be able to give approval once and apply that for each tenant's deployments. Specifically a checkbox to select which ones to approve in one go.
Source: http://help.octopusdeploy.com/discussions/questions/9189
16 votes -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
15 votes -
Allow the Deploy An IIS Website to create 32-bit app pools
The current Deploy An IIS Website step (as of 3.6.0) allows Octopus to create a website and its application pool in one step; however, unlike the separate Create App Pool step, this combined step does not allow the user to specify that the app pool be allowed to run 32-bit applications.
Since most web apps actually run faster in 32-bit mode, due to the lower overhead of the smaller pointers, and also for the benefit of people who have to support third-party libraries which are not available as 64-bit assemblies, please add the ability to set the application pool bit-ness.
15 votes -
Enable a direct link to a line in a log file
It would be really handy to be able to link directly to a particular line in a log file. So instead of sharing a URL like:
https://myoctopus.co.uk/app#/projects/Projects-539/releases/0.1.622/deployments/Deployments-11427
I could share this instead:
so that whomever I was sharing the URL with could be taken straight to the part of the log file that warrants their attention.
We use TeamCity for our builds and that has this ability to deeplink into a build log, it would be nice to have the same for our deployment logs.
15 votes -
A Visual Studio extension that will allow you to transform local config files by specifying a scope/environment
We're moving away from using Web.Development.config, Web.Staging.config, etc. filenames towards Octopus variable libraries. One of the things I miss the most is the facility provided by SlowCheetah's Visual Studio extension to right-click a config transform and select "Preview transform" - I often want to configure my local code to run in dev or staging mode for reproducing bugs and load testing.
How about a VS extension that allows you to choose a project, environment and step, and then give you a side-by-side preview of your local config file vs. the post-deployment config that would be deployed by Octopus? Showing these…
15 votes -
Show OS and Powershell version for each tentacle host
We have numerous Windows servers running the Ocotpus tentacle service. These servers are running various versions of Win2008, 2012 and powershell. Different Octopus powershell scripts have different minim powershell versions so it's important to make sure that powershell is the correct version on each server. It would be very helpful if we could see environmental info such as Windows Version and Powershell version for each tentacle machine (perhaps on the machine settings page in Octopus)?
15 votes -
Run child steps on different roles
step 1 remove web server from load balancing server(s)
step 2 deploy website
step 3 add webserver to load balancing server(s)similar to http://octopus-deploy.tenderapp.com/discussions/problems/15836-powershell-child-step-cannot-be-executed-on-octopus-server
and
https://github.com/OctopusDeploy/Issues/issues/64115 votes -
Please support deployment to Azure Cloud Sevice (Extended Support) targets
Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
Please add support for this type of targets.14 votes -
Support multi-package deploy steps
Allow package deploy steps to select multiple packages that are deployed in the selected order (with the ability to change the order). We have a website where we deploy a clean copy of a vendors files (makes upgrades easier), then we overlay different 3rd party modules and our solution into the same folder. These packages together create a whole website.
14 votes -
Visual compare of variables between releases
There seems to be no way of comparing variables between releases. Having this feature would give confidence that only expected variable changes make it into a release
14 votes -
Allow version templates to be applied to NuGet package versions
Currently (Octopus 3.2), I can choose to have a release's version number use a template, or to use the version number of one of its NuGet packages. What I would like to be able to do is apply a release version template to a Nuget package version.
For instance, if my NuGet package is named MyApp-1.23.456.7890-rc1, and I want the release version number to be 1.23.456, I should be able to set a template such as #{Package.Version.Major}.#{Package.Version.Minor}.#{Package.Version.Patch}, or #{Package.Version.Major}.#{Package.Version.Minor}-#{Package.Version.Tag} to produce 1.23-RC1.
14 votes -
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…
13 votes -
Allow project-level opt-out of "Apply retention policies"
When deploying a project that is composed primarily of a large number of Nuget Package steps (say 50 or more) the "Apply retention policy" step that runs after all packages have been deployed can take a significant amount of time to run, which slows the deployment down (seen ~10 mins).
While it may make sense to help optimise this by breaking the process down, it would also be useful to disable the retention policy from being applied, and allow it to run overnight or when deployments are not taking place. If 10 deployments like this run a day, this can…
13 votes -
Verbose logging of PowerShell script
My deployment process includes a PowerShell script process. From there, I execute another script (part of the app package) with the -verbose switch/argument.
Yet the verbose output is not captured.
It is my assumption that when Octopus runs the process script, it does not include the verbose switch/argument, and thus the verbose logging is being "swallowed" / ignored.
PowerShell scripts should include an option for VERBOSE logging
Write-Verbose within PowerShell should be captured (and accessible) SOMEWHERE
13 votes -
"Try Again" on a deployment resets "Deploy to a specific subset of machines"
When a deployment fails and must be retried, clicking "Try Again" brings up the screen with all the original settings for the deployment with one exception - the "Deploy to a specific subset of machines" section has been reset and will include all machines in the environment.
This could easily result in deployment to unintended machines.13 votes