314 results found
-
More complex filtering on machine Roles in step definitions
It would be really handy to say execute this step on all tentacles with the role 'FrontEnd' and 'Admin', or 'FrontEnd' but not 'OldOS'
As it is we are managing a whole bunch of roles and tags because some applications in a project can only be deployed to machines with a newer OS and some can only go to a Task server and some only to in internal server. NOT or AND would seriously simplify the 30 odd tags we have now :)4 votes -
Retention of NuGet Packages on the server for x releases.
If I want to delete a set history of NuGet packages like keep the last 20 packages on the server (Currently the only option I have is retention of number of days.) Is there a way to keep a clean-up of the NuGet based on the x number of historical packages that are needed for historical purposes?
4 votes -
Machine Roles: The ability to 'define/manage' these
Hi
I'm using Octopus but the one thing i find a potential problem with is the ability to arbitrarily assign a machine to any role i type in.
I would like to see the ability to have a 'machine' roles 'table' that needs to be setup before any machines can be added to a role.
That way, machine roles can be managed (CRUD functionality).
Thanks!
4 votes -
Flag to show if a Secure Variable has been set
Currently there is no way to know if a secure variable has been set or not. Often times larger companies rely on other departments (prod control, ops, etc) to set sensitive variables, whereas the developers set the install steps for their application. There is no way currently to know if a secure variable has been set when deploying to an environment.
4 votes -
Have a textarea for "notes" when promoting a release to an environemnt
In our setup, TeamCity creates and deploys a package to the "Test" environment. Then upon approval, a specific package will be promoted (by a human) to higher level environments (i.e. QA and Prod).
We need to write notes when doing so. i.e. Who approved it, etc.
4 votes -
add support for project specific environments, roles etc.
We intend using OD for multiple clients which have multiple environments each. It would be nice to be able to scope environments, roles etc to one or more specific projects or to have some kind of client scope.
4 votes -
Allow running Execution Containers directly on a Kubernetes cluster
Allow running Execution Containers directly on a Kubernetes cluster without a configured worker.
The blog post here describes how to run workers on a Kubernetes cluster: https://octopus.com/blog/kubernetes-workers However, this approach has some challenges because it uses a long-lived container on the cluster to do the work.
It would be great if we could get an option to run ephemeral Execution Containers directly on a Kubernetes cluster without the need of a worker. Or, if instead of having long-lived worker containers on the cluster that directly run tasks, the workers only acted as a "broker", and tasks using that worker launched…
3 votes -
Cloud: Support my local time zone
I would expect there to be a place in setup where I could enter my local time zone. Then subsequently all dates/times would display in my current time zone. This would include dashboard dates/times as well as Release Versioning.
3 votes -
Add dates range in Octopus task filters
if we can have date filter in the task section then it will be ease to get the data for a particular time period.
TASK ---->Advanced Filter
3 votes -
Support toast messages
It would be useful to notify either all users, a team, an individual of some changes (step template to be deprecated, upgrade occuring) via a toast/message on login so that important messages related to Octopus/deployments are delivered via Octopus directly to the users that need to know.
3 votes -
Import variables from .config file on project setup / first run
When setting up a project for the first time, I manually copy and paste variables from config files (appSettings and connectionStrings) and it would be useful if I could have them imported and set to the value from the config during setup or on first deployment to QA / first environment. Given a large number of variables, this will be where most time is spent during project setup.
3 votes -
Octopus Cloud - Packages - show total amount of space used
It would be nice to be able to see how much space packages are taking up for an Octopus Cloud instance and whether you are reaching the max amount allowed. The maximum space allowed in Octopus Cloud is not documented I believe.
It might be helpful to have this knowledge so we know when to use Octopus Cloud's built-in repository to host packages versus utilizing an external package feed from elsewhere.
3 votes -
Allow customisation of the CSP Security Header
Or let images come from any source.
3 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 -
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 -
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 -
Allow wildcards in subscription fields
For installations with lots of things it would be helpful to filter subscription events by wildcards. For example, "Prod*" environments to include all production environments.
3 votes -
Make it possible to specify the version of a step template
I've just installed the File System - Clean Directory step template from the community library and I'm getting the error listed here - https://github.com/OctopusDeploy/Library/issues/588
It would be useful if the UI allowed me to choose an earlier version of the step template as I now can't use the imported version. This would also be a concern if I had just updated a step template and the new version didn't work for some reason, I have no way to go back to the previous version.
3 votes -
Change the ReleaseEdit Role
The ReleaseEdit Role permits for updating the release variables, but it also allows for editing the release version, the deployment package that it deploys, and the Release Notes.
The ability to update the release variables should be a separate role, say: ReleaseUpdateVariables, from editing the release version and package versions.
ReleaseEdit should cover updating the release version, and the deployment package version it deploys.
I'd also suggest adding third role for updating the release notes: ReleaseupdateNotes for appending to (but not otherwise modifying) the release notes.
The idea is that different user should be able to be responsible for updating…
3 votes -
Automatic, on-demand regeneration for server<->tentacle certificates
As per https://octopus.com/blog/shattered
SHA1 -> SHA256 upgrade is currently manual (or custom scripting). It would be good if Octopus could manage certificate regeneration on-demand, with an option to choose an appropriate, current cipher.
3 votes