314 results found
-
Allow variables to be moved between sets/projects
When setting up new projects, it can often take some time to get variables into the right places, whether they be tenant-specific or project-specific, usually there is a bit of trial and error involved before you can determine the right place to locate these variables. This involves copying variable definitions from one screen to another, then deleting the original.
Would it be possible to alter the variable definition to be able to 'move' it from one set to another, or to a specific project, so that not only does the definition move, but also any values held for the definition?1 vote -
Disable built-in NuGet feed
I'm using an external NuGet feed and I want to be able to turn off (disable) the built-in NuGet feed.
1 vote -
Control what is the default NuGet feed
I want to have an external NuGet feed as the default selection when adding steps to the deployment process. Can't seem to control that anywhere.
1 vote -
Less clicking, more doing
There is way too much clicking and scrolling that needs to be done in order to manage/administrate/setup a deployment process.
Some examples:
Change the name of a deployment project, but don't save yet. Click the button to upload a new logo for the project. You get a warning about discarding changes. Why? I'm not done changing my project settings.
There's a little "hamburger" menu on the left side of each deployment project process step. But it's useless. For example, why not have options in the menu to "Run in parallel with previous step" or "Run after previous step" (the opposite…
2 votes -
Allow scriptable health check to be based on percentage of remaining free space
Currently $freeDiskSpaceThreshold can only be specified as a static value.
We have many machines that have a mix of large and extremely small drives (MB). There is no way to define a machine policy that does not cause health warnings on these machine.
If we could specify a % value, that would solve the issue.
1 vote -
Mark an environment as Tenant-only
Workaround at the moment would be to only have deployment targets that have been assigned to the Tenants that are connected to the project.
1 vote -
Allow us to use variables in the Package ID field of a template step
We've created a step template for the deploy package step and we made the Package Id a Parameter. This works, until we assign a variable to this field e.g. #{MaintenancePackageId}, in which case the package id doesn't get expanded. The same seems to happen when using the variable directly in the step template without exposing it as a parameter.
The package #{Maintenance_package} could not be located in the built-in repository.
Plus, when using the step template and a parameter, the description of the step shows
"Deploy package #{ParameterPackageId}"
instead of the value being passed in. It does get executed directly…
4 votes -
KickStart Templates
Hi,
It would be great if you can create "KickStart templates" for the most demanded packages
1.OctoDeploy Pack for Nopcommerce on Azure
2.OctoDeploy Pack for Umbraco on Azure
3.OctoDeploy Pack for Dotnetnuke on Azure
4.OctoDeploy Pack for Sitecore on Azure
5.OctoDeploy Pack for Kentico on Azure
6.OctoDeploy Pack for ViennaAdvantage on Azure
7.etc etcbecause its a nightmare to get this setup in multi staged environments even for experienced development teams
the sad part is, many startups/small companies do not have deployment,cloud admin teams as a separate resource. all the work are done by the development team itself. for them…
1 vote -
Self signed certificate with SHA256
Today, (Oct16), OD makes use of 2048, SHA-1 self-signed certificates, valid for 100yrs. Do not use SHA-1 as the signing hash. This is considered to be a bad practice and soon some web browser might stop supporting it. Please change to use SHA256 to mitigate this.
1 vote -
DataProtectionScope.CurrentUser
Today (Oct16), the Win protection of OD's MasterKey is using DataProtectionScope.LocalMachine, i.e. any process on the local machine may unprotect the MasterKey stored in the file OctopusServer.config.
I would like to be able to configure OD to have the MasterKey protected using DataProtectionScope.CurrentUser. If so, I could run OD (, Manager as well as Portal,) using a specific Win user and only this user would be able to access the MasterKey on the local machine. Thus, this would increase the security, which is important for us.1 vote -
Apply channel restrictions to life cycle phases
Now that we are starting to embrace channels, we are finding that we want to limit which channels can go to which stage in a lifecycle. For instance, we have two channels - master and pull-requests. Pull Request (aka deployment per PR) can only go to the Staging Environment, but the master channel can go to Staging and Production.
Right now we have two life cycles to make this happen, but that causes a lot of extra life cycles.
3 votes -
Add global steps
I have come to find almost all of the project steps for my applications follow a general pattern:
Deploy package
Do clean up
Configure
Send EmailIf I could encapsulate steps similar to Variable sets so that I can include them where needed, this would actually cut down on my maintenance requirements by a ton. I see this as kind of a rules engine. So...
"When a package is deployed..." do a step before the process is allowed to continue.
"When a project is released..." do a step after the process is done.All of these would be able to…
1 vote -
Navigation and updates
For enterprise users with a dozen teams sharing an instance of Octopus, navigating and making updates is pretty cumbersome. So for instance, we have over 20 life cycles, so if I make a change and save, I get sent back to the top of the list so that I then have to scroll back down to the life cycles I'm interested in. Environments is even worse, with over 70, but only 6 I care about. Some filtering on the pages or just a top level line of business/division filter would be great.
1 vote -
Separate lifecycle phases
I find it confusing when we have all the stage environments and production environments inline.
I'd love to see the phases separated into different rows.
Example: I have two phases, Production and Stage.
https://i.imgur.com/1zU4KG0.png1 vote -
Warn users when changing main Project Lifecycle when there are Channels
We changed the main lifecycle of the project. The project had a channel defined which was set as the default channel which was using the same lifecycle as the project. There is no indication when changing a project's lifecycle that the underlying channels are not updated, except for a cryptic message below the lifecycle selection which can be read as "There is a small possibility that in certain circumstances someone may have defined a channel, in which case what you see here may not be what is happening in reality. We'd really, really love to get a warning or at…
1 vote -
Clearly show the phases of a lifecycle on the dashboards
The dashboards show each of the environments to deploy to, but they don't indicate which are part of each individual phase of a lifecycle. This means if we need to deploy to one of five environments it can get a little confusing without a really clear environment name.
I propose that we draw a line divider in between the phases or colour the environments within a phase differently from each other.
3 votes -
Enable Octopus server to be deployable via machine image
Is it possible to create an AWS AMI using Hashicorp Packer with Octopus server installed? Is there any guidance or documentation? We're finding it a bit difficult.
3 votes -
Rename "Service accounts" to "API Accounts"
The term "Service Account" is massively overloaded in the technology world. It is most commonly used to refer to Active Directory/LDAP accounts used by services, and thus can be very confusing when using the term in communications. Renaming it to "API Account" would help to differentiate it from the accounts the Website runs under.
1 vote -
Save Step Templates as Powershell instead of JSON
The current JSON style templates makes it somewhat difficult to manage updates and changes. When comparing a template exported from my Octopus server against one from the community library (or GitHub), most of the metadata properties are the same and aren't interesting. What's more interesting is comparing the actual Powershell script changes. But having the script embedded in a single line of JSON makes it extremely difficult to actually make a comparison to see what really changed.
Furthermore, in our organization, when we want to make a change for a template in our GitHub branch, pull requests are difficult for…
21 votes -
Support standard keyboard shortcuts
Keyboard navigation isn't always usable in the web UI of octopus deploy. I find myself hitting ctrl-s regularly expecting that things are saved, ctrl-c or specs to leave a pop-up without saving etc.
3 votes
