1458 results found
-
Ability to restrict deployments on certain days and/or between certain times
It would be nice to be able to restrict deployments to certain environments ( for instance the production environment) from being able to happen on certain days/times. IE only at weekends or only after 8pm
At the moment I use a powershell script which just throws an exception which stops the deployment but it would be nice to have this built in. Especially if it could be linked with the "Schedule a Deployment" idea. Then if someone tried to deploy it could say unable to deploy at this time do you want to schedule for the next available time.
13 votes -
Show the total duration for a task when the log is collapsed
When collapsing a log entry/header for a task it would be great if the total duration was displayed. That way it would be easy to spot slow tasks in a full deployment.
2 votes -
Check signatures on NuGet packages
The weak link in deployment with Octopus is the NuGet repository - a bad guy could upload a package that leaks your sensitive data, and Octopus would deploy it without realizing.
A solution would be:
- You sign your NuGet packages with a private key X509 certificate (NuGet uses System.IO.Packaging which supports signatures)
- In Octopus, you provide a list of thumbprints of certificates that you trust (e.g., you only trust NuGet packages signed by yourself)
- When Octopus downloads a package, or when Tentacles download packages, Octopus verifies that they have been signed by a trusted certificate
This should be an opt-in…
19 votes -
Guided Failure Mode
The guided failure mode is a very nice feature and we use it a lot. One improvement that our Ops guys would like is better visibility on when a failure occurs.
For example, we have 30 steps and as the deploy is progressing the top of the page is not visible.So, when a failure occurs that needs to be addressed you don't really know about it until you scroll to the top, because when the top of the page is off the screen there is nothing that indicates a problem.
The only way you know there's an issue is by...…
3 votes -
1 vote
-
Allow specifying which Project Groups have access to Environments
I have different applications that deploy to different sets of servers. I could create unique environments to handle the separation but it could get ugly pretty quick. If a project group was tied to a set of environments it would make it easier to know what environments apply to that project and prevent me from selecting the wrong environment to deploy to.
3 votes -
Enable rpd connection creation, Amazon style
Enable double click or something like that on a Tentacle machine in the environment overview. When you click/doubleclick/other then adownload is started with a preconfigured rdp file.
Just like you do on amazon.
This way its easy to open a connection to a specific tentacle and octopus only has to create a downloadable rpd file, with server name and possible pre filled domain/user,
VERY nice feature for handling your servers and apps :)2 votes -
Allow the create or modify "IIS web site and application pool" step to only create
I really like the new feature where Octopus can create or modify the IIS web site and application pool. In some cases an administrator may want to change some of the configurations on the web server which shouldn't be changed on the next deploy.
I would like to be able to configure this step so that it will only create the IIS web site and application pool if they don't already exist.
2 votes -
Add release quality properties
Add a concept of release quality. One should be able to define (per-project) a number of quality dimensions (e.g. regarding unit tests, performance tests etc.). Values in each dimension should have absolute order. Than, for each environment one should be able to define a minimum quality level for each dimension that a release need to have in order to be deployable e.g. for UAT environment both unit and integration tests need to pass and for PROD also the performance tests need to be OK. The build quality would be editable via UI (e.g. by a QA person) and via the…
3 votes -
Add extensibility to UI and data layers
Add support for custom pages or widgets that can be added to the Octopus Server installation along with custom fields that can be assigned to Project and Release. An example would be a NUnit widget that could use API to fetch NUnit test results artifact and format it nicely on release page. Other example could be storing 'build quality' property along each release. The value would be updated e.g. by the build server after executing unit tests or integration tests or a QA person after doing some exploratory testing
3 votes -
Implement a full nuget server (support for VS integration) with caching and plugin-arhcitecture to support data retention
Implement a full nuget server (support for VS integration) with caching and plugin-arhcitecture to support data retention.
This could perhaps be a seperate product. The key is that it should supports internal hosting, is fast, manageable and queryable via an API.
Yes we can look at the Nuget Server source code and build it ourselves, however managing open-source package deltas is not part of our core duties
6 votes -
Ability to set appSettings and connectionString values that don't exist already
I make extensive use of appSettings values in my app, but I do not want to include every single value that can possibly be set in my source repository. I would like Octopus Deploy to allow me to set appSettings and connectionString values that will get inserted into the config if they don't exist already.
7 votes -
appsettings
Add XmlPoke functionality for setting various config values.
1 vote -
View/edit permissions from users and groups view
Right now, we have to add/edit/view permissions at the permissions view. The test feature is pretty cool, but sometimes I need to quickly check a user's permissions. Right now I have to search all the groups to see what groups they belong to, then switch to permissions view to check the group permissions.
It would be much nicer to see the list of permissions when I view the user or the group.
Additionally, permissions have to be added one at a time and then re-ordered.. it's very tedious when setting up a new project!!!
3 votes -
Disable variables
It should be possible to mark a variable as disabled:
http://help.octopusdeploy.com/discussions/questions/1788-disable-variables-option
10 votes -
Global deploy.ps1 or have a tentacle deploy.ps1
We have created a deploy script that we use as standard on all of our projects. However we do have to include it in all of our projects. The only difference is the variables we pass to each project.
It would be great if deploy.ps1 could live on the tentacle and execute that if the project doesn't have one. Or possibly chain them, tentacle executes its deploy.ps1 (if one exists - maybe a project option to skip it), then execute the project level deploy.ps1 (if one exists).
This would save us time having to include it (ok its not a…
3 votes -
Manage VPN connections
Make it possible to put machines into a VPN connection, and have Octopus manage the closing/opening of the connection so that concurrent deployments don't result in closed or hanging connections.
27 votes -
Search/Replace Virtual Network node in Azure cloud configuration file
In the Cloud configuration file for Azure deployments you can specify VirtualNetworkSite to determine which network the role will be deployed to. It would be great to be able to specify this in Octopus.
An alternative is to specify which service configuration (default Cloud) to use for the deployment/step.
3 votes -
Latest release should be highlighted.
The latest assembled release should feature more prominently on the releases page, at present it is at the top of the recent release list, but it does not jump out at you, The latest release should appear to the left of the currently released versions. when you click it you should be taken to the deploy page.
3 votes -
Add richer dashboard experience by allowing user to promote, create releases and detect changes.
On the dashboard, when hovering over a successful build an arrow should appear next to it with the word 'Promote' clicking this button should start the deployment to the next environment in the chain.
On the dashboard, when OD detects there is a new version available on the nuget feeds, a small + symbol should appear next to the project name, clicking this should take you to the create release screen.
7 votes