1458 results found
-
Sub steps to inherit the environment settings from the first step
In the process definition for a project it would be really good if the sub steps under a step with sub steps could inherit the environment settings from the first step – at the moment you have to set the environments on each sub step.
1 vote -
Interface for Powershell script generation
True. Powershell scripting is a powerful way of achieving more customized deployments. But not all will be well versed on scripting. Instead provide them with a UI which transforms their actions into powershell scripts used in deployments. And users can add more and more value to add by adding more actions thus making anything possible with respect to deployments. Scenarios might include taking machines out of load balancing and deploy set of services/applications and then joining them again and redo ing it for other machines. Improved and custom logging
1 vote -
Email Octopus Administrators if a Backup Fails
I'd like to see an option added to the Configuration -> Backup tab to send an email to users in the "Octopus Administrators" team if a backup fails.
1 vote -
Have type of promt variable
It is really great to be able to add some promt variables but it could be really usefull to have anything else that just a freetext field.
The main useful types could be checkboxes, radiobutton, dropdown list.Regards,
Benjamin V.1 vote -
Allow you to see all releases a specific package was deployed to
We would like to see all the releases that contain a specific version of a package, therefore able to track what environments they were deployed to as well as its history. When we may be debugging you can get the version of a binary and then be able to track the package and when/where it was deployed.
1 vote -
Allow for expiration of users in a team
We have a need to setup a Production Release Day Only team, and right now we add users to that on production release day, and then have to remember to remove those users, because we don't want them to have access to production forever. It would be nice if a team could be created that has a configurable number of days where any users in that team that have been in that team for more than that configuration would automatically be deleted from the team.
1 vote -
Render markdown in package descriptions
With Octopus 2.6.4 this is partially implemented. You can see the markdown in package descriptions rendered when looking at a release.
It would be nice to also see it rendered in the Library.
This is extremely useful for embedding links in my packages to point back to the build and commit used to create the package.
1 vote -
Clearly display the version you are licensed for and when the support expiry is
It would be great if you can easily see what edition you are licensed for and when the expiry for support is.
Having it hidden in the Licence key area is not easy to see.
1 vote -
Group scripts in the Octopus Deploy Library by Category
As the number of scripts in the library grows it will be helpful to add more structure to it using categories and/or tags.
Add a "category" and "tag" field to the metadata for each script in the Octopus Deploy Library.
Change the UI to group scripts by Category.
Initial categories could include:-
Workflow (Wait, ...)
Windows
NT Service
IIS
Database
Test (NUnit, Http request, ...)
Data Collection (Disk space, CPU, ...)
Integrations (Slack, Hipchat, ...)
Network Environment (Load Balancers, CDNs, etc.)1 vote -
Allow Deployment Scenario Step Presets
Our deployment targets encompass 100+ tenants, so our deployment process encompasses multiple products within a consistently versioned suite of products.
When we upgrade a client, they receive all components within our suite. However, some of our products support the ability for styling customizations that we like to flow through our standard/normalized release process -- these customizations get versioned in a distinct nuget package and can be redeployed within a release version. This means that our product version is redeployed multiple times for a given client if a new customization is created for a client.
So our deployment process for this…
1 vote -
See a list of variables that will be used/has been used for a given release
For debugging purposes it would be extremely useful if you could have a list of variables use for at given deployment or what variables were present at creation of the release.
1 vote -
Step Template Updating Settings should not cause a new version
As I've gotten more and more step templates, I've realized that there are some of the step templates that I'd like to rename to make it easier to "group" like ideas. The problem here is that as I refine these, each renaming creates a new version. The same would be true of the description. This doesn't seem like something I should be running out to each process to update especially since the name wouldn't update anyways.
1 vote -
User description
Something I would like to see is user description. We have a few service users and since there is no description we are using a mix of display name and a page in confluence to describe their roles and scope.
And what about having a place to store API keys? Only available to certain roles, let's say system administrators.
1 vote -
Implement "PLATFORM" concept
We are using Octopus and different platforms with different environments.
we have 4 platforms, each platform has 8 QA environments and 1 production environment.I would like octopus to implement the "Platform" concept. So you create at platform, in that platform you create environments. Projects are living inside the platform(Like today). You should be able to scope variables to a platform.
1 vote -
Display which version of Powershell the scripts work on in Script Templates
In the step templates, show which version of PowerShell the scripts work on, be useful to look at a glance and see which version they work against - the MSMQ - Create Transactional Queue only works on PowerShell version 4 and higher.
1 vote -
Project config to have all servers disabled by default
There are times where a release only has to be deployed only to a subset of machines, which can be achieved using the "Deploy to a subset of machines" option. But by default this option has all the tentacles enabled which could cause problems if the user doesnt disable all the machines that he doesnt want to deploy to.
It might be a good idea to add a config to the project so the subset of machines is set to "none" instead of "all machines", forcing the user has to hand-pick them one by one.
1 vote -
Allow a user to select which team they are operating under after login
The same user may be assigned to different teams, and would like to have the set of projects and environments that are displayed on the dashboard to be filtered by which team the user is currently acting as a member of. For example, user Bill is a member of the Sustaining Team and also the New Development team. He would like to log in and then choose the Sustaining team as the team he is operating under for that login session, so that he then only sees projects and environments that are relevant to Sustaining Team members.
1 vote -
Pass environment parameter list of sensitive variables
Pass an environment variable to deployment PS scripts that lists the names of sensitive variables. We would like to mask these in our file logs and currently only have the choice to output NO variables or worse, log the sensitive variable values.
1 vote -
Allow Parameters to be grouped in Step Templates
Each step template parameter appears next to each other on the UI and there is no way to group them as far as I can see. It would be nice to have a way to group parameters and display them nicely inside the UI.
1 vote -
Use a web resource as a proxy for a listening tentacle
I'm working in an environment where web servers are sitting in a DMZ that only allows incoming HTTP traffic - no outgoing traffic at all is permitted without going through numerous administrative channels to get ports opened. I do however have full administrative access to the server only.
I could deploy a tentacle in this scenario if I had some kind of web resource that acted as a proxy for a listening tentacle. Octopus would manage the tentacle via <site>/octopus-deploy.axd instead of through the usual listen port.
1 vote