1458 results found
-
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 -
Add tenant tag support to runbook scheduling
Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.
11 votes -
Give ability to create and store custom accounts
I want to be able to easily store and use other cloud providers. At the moment only Azure and AWS is supported but I want to be able to use others. The ability to create others (such as DigitalOcean) would be brilliant.
I would be happy being able to store the key and secrets and have Octopus set the values in the worker as environment variables that I specify (it would also be very useful to also be able to say that this variable is an environment variable rather than needed substitution).
1 vote -
BUG: Resizing web browser deletes unsaved form data
When filling in a form in Octopus Deploy, for example to add a deployment step or to add new variables, if you resize the window all unsaved data is lost.
Whie I acknowledge this is unlikely to affect many people, I've hit this a few times when taking some screenshots for documentation purposes. It's fairly annoying.
I think it happens when the page switched from one responsive layout to another. For example, when the project sub-menu hops from the left side of the screen to the top of the screen.
1 vote -
Add parameters to Runbooks
This would be like runbook specific variables, but they are defined on the runbook and don't make sense to be in the published snapshot. They would generally be prompted values, but that shouldn't be required. They would be "snapshotted" when you run the runbook. When you are scheduling runbooks with a trigger, you should be able to provide values to use when the runbook is triggered.
For an example use of these, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email…
8 votes -
Show worker name in Task Log
Please add the name of the worker machine to the task log when a deployment is made. It is a small change which I think will be easy to add.
Reason/Rationale/Context: We were working without workers/worker pool and we just had a few deployments that we were setting up to run on our Octopus server. My colleague added a worker and without me noticing what I thought was running on the Octopus server was moved to the worker. I knew I had the dependencies my script needed installed via Octopus on the Octopus Server (like a trusted root certificate and…
1 vote -
deploy EAR/WAR on IBM WAS ND 8.5/9.0 cluster
Dear Sir,
request you to make setup of IBM cluster - two mode ( one cluster for DEV and another for UAT ) then request to install any EAR ( not WAR) record then replication/substitute for UAT fully scripted way using python/Jython. -
Regards
Anis1 vote -
Allow setting Build Information WorkItems
Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.
Please allow Push Build Information API and Command line to
- Set WorkItems with values set on request
- Do not override values even if Issue Tracker extension is enabled5 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 -
Change the CLI to fail if the --skip step name does not exist
When our Azure DevOps build runs it does a deployment to our Dev environment and specifies step names to skip with the Octopus CLI and the --skip argument. However there is nothing stopping someone from renaming the step in the Octopus process which then means we're no longer skipping the step. I would prefer that the Octopus CLI fail when doing a deployment with a --skip step name that does not exist in the process.
1 vote -
Execute adhoc data updates with sql on Jira
Hi it would be useful to have execute scripts feature on Octopus for data config changes to be picked from jira.
This will help to select dev env and validate SQL and use as test evidence to run on prod env.
Auditing abilities on octopus can be further enhanced by attaching script execution to Jira also. All major releases have database changes along with binary deployments, it is imperative we keep audit history for data changes also.1 vote -
Create a customizable drop down list for favorite projects (per user).
We have hundreds of projects in dozens of project groups in Octopus. As a DevOps engineer I have occasion to work with many projects over the whole system.
The filter by project and project groups are helpful. But what would really be helpful is the ability to go into a project - hit a * to make it a favorite, then on the dashboard tab have a drop down list of all my favorites that would take me directly to those projects.
2 votes -
Create RPM packages for Calamari
For Tentacle deployment targets on Linux, you make RPMs clearly available: https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle
However, for SSH deployment targets on Linux, there is no RPM (or apt, etc...) for the Calamai package. Most Linux admins (rightfully) like to manage deployment targets with Puppet profiles, or similar, and the idea of manually installing Calamari directly on the servers creates configuration drift, and goes against most devops principles.
Could you make binary packages available for Calamari like you do for Tentacle?
2 votes -
Let users select apps to deploy for a Jira issue
Currently our workflow for indicating/knowing what app/s need to be deployed for a Jira issue or a Jira release (of multiple issues) is to manually enter/bundle up these from the Jira issue descriptions which we fill out.
What would be amazing though would be if the Octopus Jira integration plugin rendered a smart "section" into the Jira issue, where you could (1) select which apps need to be deployed (from Octopus), and (2) then get a read-only envs+releases matrix like in the octo dashboard so people can see where it's deployed currently.
Furthermore, on the Jira release/deployment page (assuming this…
1 vote -
Allow worker pools to be compatible with ALL process steps
Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.
2 votes -
Allow middle mouse button click or ctrl + click to select items in search dropdown.
In some previous version of Octopus, I was able to do this. I always used the search dropdown to open up multiple projects at a time using middle mouse button click.
1 vote -
Project Group as collapsible panel (like Expand/Collapse)
Can we add collapsible panel (like Expand/Collapse) to Project Group. Most of the time I have to scroll down to search my projects, so it would be easy if we add expand collapse section.
2 votes -
Execute F# script steps using dotnet fsi
Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.
Switching to
dotnet fsi
will allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/5 votes -
Permanent fix for Octopus-Jira integration to evaluate release notes for dynamic pckages
Permanent fix for Octopus-Jira integration to evaluate release notes for dynamic pckages.
This is critical for end to end visibility in Jira.
2 votes -
Allow a "not" mode for filters
We have a dev cluster set up and working with octopus.
One of the hurdles to creating ephemeral/adhoc debug/testing environments at the moment is the fact that we have to go in and manually map those environments in lots of different places.
Ideally, we'd be able to create a resource (e.g. a kubernetes cluster, certificate, etc), that lets us specify that it is a valid resource for ALL environments EXCEPT production.
2 votes