314 results found
-
Package Library Wildcard Search
When searching for a Package in the Library permit the use of wildcards to optimise the searches.
We have prefixed our packages with the names of our clients and it would be great to view all packages where acme* would return all acme packages
1 vote -
Add the ability to group tenants
I think it would be a good idea to have the option of grouping tenants for the purpose of organisation and not deployment:
- A group does not have the functionality other than to group items
- Grouping is optional and you would always be able to interact with tenants in the same way you do now
- Groups have a name, description and maybe an image
- A group can contain tenants and/or other groups
- Tenants do not need to be in a group
- Being in a group does not functionally affect the tenant
The scenario:
- I run a business that puts up…
1 vote -
Filtering tasks for Success with Warning
The Tasks screen has various filters, but the appears no way to filter to display only the Successful task that had warnings. I was to be able to audit warnings periodically to uncover common flake issues and maybe address them.
This is using v2018.3
2 votes -
Allow customisation of the CSP Security Header
Or let images come from any source.
3 votes -
Tenanted Variables
After upgrading to this new version of Octopus, with the new UI, the configuration of tenanted variables became very counter-intuitive, it's very heavy while loading multiple projects and the color pallet makes it even harder to understand which environment is which, but the color pallet it's an issue in general with all of the UI of this new version, it's very confusing as you cannot distinguish easily between projects, tenants, variables, environments, etc.
1 vote -
Additional Filteroptions for the dashboard
Currently the dashboard can get quit full if you have a lot of applications even if you sort filter them by project. It should be possible to filter the dashboard by more optiones then just project.
Ideal filteroptions would be Timestamp of deployment, Timeframe for deyploments, environment, other tags like traget roles.1 vote -
On Dashbaord always show Environments & Projects
When working with a large number of projects & environments, it easy to get lost if you are scrolling horizontally and verticle, If you were looking for a specific project in a particular environment.
1 vote -
Expand All GUI by default
Have a checkbox in v4.x in the users profile to default expand all. This is the biggest visual shift from 3.x to 4.x, is the collapsing of content.
5 votes -
Audit on step template
Today we had an situation that somebody changed shared step template. We were more than surprised when we found out that there is no audit on step templates and we were not able to check who messed up. Please add audit there.
3 votes -
Style editable text boxes to have some visual cues as to what is clickable
Text boxes (for example, the notes on manual intervention steps) give no indication of which part is clickable to focus the text box. The obvious places such as at the top of the white area or in line with the grey text that looks like a placeholder both do precisely nothing
1 vote -
Octopus Server, One Click Update / Upgrade option
We use JetBrains TeamCity along with Octopus Deploy and TeamCity included a "one click" upgrade process for point releases in their web application. This is a very useful feature.
Just in the last 3 weeks 8 minor point releases have been made available for install.
I suggest Octopus includes a similar option for simple updating of the Octopus Server to the latest available release. We see the notification in the web interface right now, but a method to click and have it backup recommended configurations and update the installation would allow our Engineering teams to keep the instance more current.
3 votes -
parallel processing
We're using the octopus little bit specific way for copy databases from the Live environment to staging, dev test.. etc. including anonymization and related steps. The most important functionality is the parallel processing.
The most important functionality is the parallel processing.
Anyway, the body of PowerShell processing is in our case same.
Just every parallel running task is responsible to process only particular part.
It leads to following configuration:
OctopusBypassDeploymentMutex = $True
and cration following structur in Octopus:1 Not important starting step
2 Parallel procesing step part 0
2.1 Sub-step 1 of processing part 0 where body of script
…1 vote -
Introduce a 'stable' release feed for Octopus Server - monthly release
Hi.
I've started to look for an easy way to figure out which release of Octopus Server that can be considered stable, since my colleagues are depending on the software and they aren't pleased the amount of bugs that has been coming and going.I've been helping out on the community template
which lets the Octopus Server easily do rollbacks, in case of major bugs.
Michael Noonan suggested in this thread
https://help.octopus.com/t/overall-quality-of-octopus-server-updates-are-integration-tests-being-applied-to-octopus-server-upgrades/19214that some customers uses the latest version of the previous feature release to make sure Octopus is semi stable. I'm very aware that even a stable version…
1 vote -
Update-to-date Step Templates
When setting up a step template, if a previously added, and configured feature has been removed from the Step Template, after which all the process steps that are using it, are updated. (Under the "Usage" section)
I suggest you remove it from the applied features when running a deployment on a release. It's the WORST to debug something that has hidden configuration features applied.
1 vote -
DevOps Dashboard
DevOps Bashboard. An at-a-glance dashboard you can stick in a monitor with big numbers and charts showing all sorts of data. Could be useful for bright red error alerts, show statistics, maybe sticky a project overview. This would be a guest/read-only access account.
2 votes -
Allow OctopusDeploy to respect group membership in resource domain
A typical scenario is described here:
https://octopus.com/docs/administration/authentication-providers/active-directory-authentication
(the diagram at the bottom with a one way trust)
Per my thread with Octopus support, Octopus will not respect group membership of DomainA. This would be useful where the resource domain is managed by one group but the user domain (DomainB) is a shared corporate resource.
Thank you for your time.
1 vote -
per-project lifecycle notes
I would like to be able to provide notes as to WHY a project is using a specific lifecycle.
In my case, some of the systems being integrated with only exist in TEST/PROD (not DEV). I'd like to note the systems that don't exist in DEV so that someone doesn't incidentally try to switch the lifecycle.
3 votes -
Update the Octopus Integrity check to ignore Azure SQL Replication Schemas
Hi,
We are using an Azure SQL DB which which is geo replicated to meet our DR requirements. As part of this configuration Azure adds two additional schemas to the DB (DSS and TaskHosting) presumably to keep track of the internal replication state.
However this does cause the Octopus Integrity check to fail as it is not expecting to find these tables on the DB.I have also noticed that during upgrades (from 3.X to 4.x) it tries and fails to remove these tables which isn't causing any issues we can see at the moment but could cause issues down…
2 votes -
Specialized audit interface to easily track the changes to variables over time
It would be useful to be able to track changes to a specific variable over time across all variable sets and projects. These kinds of changes are available now in the audit logs for projects and variable sets, but are very cumbersome to sort through if you are looking for a specific variable.
I would propose an interface that lets you filter the audit log to a specific variable name (potentially utilizing wildcards as well) and limits the view to the values of that variable along with the scope and modified date. You should also be able to filter/sort by…
4 votes -
After scoping a variable to an environment, then filter the roles (target machines) to those that belong to that environment.
It doesn't make sense to list ALL target after you have just scoped variable to an environent.
1 vote