1452 results found
-
Group order the Tasks page by Active, Queued, Recent
When I have many Queued tasks and then go to the Tasks page, I have to scroll down to see the Active task. I suggest the Tasks page be grouped by Active task, then Queued tasks, then Recent tasks.
1 vote -
Ability to view Release snapshot of all variables
We need the ability to view all the variables in a release snapshot including those coming from step templates
1 vote -
Specify PowerShell Version
Ability to specify version of PowerShell during script execution.
Currently tentacles use the default path, which is great most of the time! You could currently call PowerShell with a command line parameter but any scripts have to completely re-written to work this way, which defeats the simplicity of Ocotopus!
1 vote -
usability - icon to edit project group from "projects" drop down
If I want to edit a project group, I must first navigate to the "all projects" overview page. Would be nice to just have an edit icon in the "Projects" dropdown for easier access.
1 vote -
Enable one to be able to iterate a list of last installed directory paths for steps in project
Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.
1 vote -
fallback on the instance count for Azure deployment
Today if I select to have the instance count use the count from the Azure management portal and an instance isn't pushed yet (if I had deleted it for example) then it will fail and I have to go in an set it to the value from the config file and then switch back to use Azure mgmt. I'd prefer that it would fallback to the config file if it's not deployed in Azure yet.
1 vote -
Octopus variable for Deployment Start Time for scripts
For PowerShell scripts it would be good to know the deployment start time.
This way later scripts can report how long a deployment took up to that point.
(A current workaround is to have a script run at the start that sets a variable for later use by other steps)
1 vote -
Integrated web file manager for servers
Hello
I find it important to check the actual contents of the folder i am deploying to, in order to be sure that everything worked as expected.
Wouldn't it be great to have an embed file manager to see the folders and the files of the server you are deploying to?
Every server, every environment, every project, with user management, and permissions...this would come in handy, even without deploying something really, just checking files, altering something in servers, without having to remote desktop, or use ftp etc. All centralized.
thanks
1 vote -
Configure Default Deploy Options
It would be nice if you were able to configure defaults for deploy options. Currently they are all false by default. I never really had a need to check any on a regular basis until Guided Deployments are introduced but now I find myself checking this option with every deployment, which isn't optimal. I'm not sure if it would be best to be able to configure these on a per project level or perhaps project group level but it would be nice to configure their defaults somehow.
1 vote -
Export per environment/project release calendar (ical)
It would be nice, if it is possible to export all release dates to an iCal export.
This would allow to bind those release to Outlook or any other systen supporting iCal.Currently we would like to have the export per environment but could imagine, it's also very common to have a per project view. The item must not include that many details:
- Time of release
- Release name
- Project
- Environement
- Link to octopus release page
- Maybe owner?1 vote -
Keep track of the task expansion view (all, interesting, errors, etc.)
https://github.com/OctopusDeploy/Issues/issues/804
The page should remember:
- Whether you like to look at the summary or output
- Which expansion option you are using
And default to it
1 vote -
Access control to edit Library by environments
I've setup global libraries. One is named Global which defines settings (across all environments) while i have other libraries named Dev, QA, Staging, and Prod. I'd like to be able to allow QA users have access to only edit the QA library similarly how they currently can only deploy to QA environments. They would be able
to define new variables that override the global variables for their environments to validate their testing needs.1 vote -
Allow users to view detailed output log without deployment or enviroment permissions
The current readonly roles do not let a user to see the detailed output of deployments.
In larger enterprises, the dev teams can't deploy to production. However, they need to be able to see the output.
1 vote -
1 vote
-
appsettings
Add XmlPoke functionality for setting various config values.
1 vote -
Delete files when Octopus Deploy is uninstalled from a machine.
Normally, Windows Uninstall removes all program files, except those that have changed since the install (like config files and data files).
Currently the installer does not do this.1 vote -
Make Octo.exe trace logs to the console
It would be great if Octo.exe could trace log output to the console window - instead of waiting for deployment. We integrate into a Continuous Delivery server (not Team City), and it would be good to be able to view errors in one place.
1 vote -
Add setting to project to indicate that the packages should all be the same version
Our project deploys multiple packages and always uses the same version across all the packages per release. It would be nice to have a setting at the project-level to indicate this. This setting could allow the user to select the version once when creating a release and help prevent the user from accidentally entering a different version for one of the packages.
1 vote -
List variable names from .config and .ps1
If octopus could scan packages for variables from Web.config, app.config and xxxDeploy.ps1, looking for appsettings and connectionstrings and $OctopusParameters[]. Then when adding variables it could suggest variable names. But also when creating a release it could warn about new settings/variables that have been added since last release and for which there was no variable?
Maybe it would actually be octopack that scanned for variable names and provided it as metadata in the nuget spec?
1 vote -
Component centric dashboard versus release centric
Currently we have a couple ways to deploy. A main deploy which deploys our entire system 20 components (a service, website, etc) in one release. And adhoc deploys, deploys one component at a time. It would be nice to have a component view versus a release view the main point would be to show the state of each component and what version they are on.
1 vote
- Don't see your idea?