1457 results found
-
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 -
codebuild
Add an official Octopus plugin for AWS CodeBuild to integrate with Jira.
https://octopus.com/docs/managing-releases/issue-tracking/jira#availability
5 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 -
prompted variable calculated default value
Allow the default values for prompted variables to be calculated, instead of a constant.
4 votes -
'dotnet octo pack' multiple packages in one command (Octopus.DotNet.Cli)
The OctoPack project is great for Framework projects. We add the nuget dependency to select projects and add
/p:RunOctoPack=trueto our build script. The build script does not need to be updated for every new, removed or renamed octo-packed project.SDK projects are less automated. After building, we have to run
dotnet publish, thenocto packfor each project. It would be great to define 1 build script, then update the projects as needed to pack or not.Idea to attain goal:
Add element
<IsOctoPackable>true</IsOctoPackable>in csproj that works similar to IsPackable.Allow
dot net octo packto point…
5 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 -
Connect project to many tenants at once
There is currently no way to associate a project to multiple tenants without going into each tenant one by one, finding the project, selecting an environment, and clicking Save. For installations with many (tens or more) tenants, this is quite inconvenient, and has resulted in hacky workarounds from third-parties.
16 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 -
JSON Template for Subscriptions
Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)2 votes -
Expose Octopus.Deployment.Targets during deployment
The current Octopus.Deployment.Targets variable is only available to the Deployment Changes section. It would be beneficial to expose this information during the deployment too.
The use case in mind is sending emails pre-release that mention the machines that will be deployed to, or in the case of Azure, could expose the URLs, given these work on the convention of <machine-name>.azurewebsites.net2 votes -
Allow variable in variable set to have a Project Group scope
It would be useful if we could set variables in a variable set to a Project Group scope.
The use case for this is that we have a shared variable set that sets a product ID.
We could then scope this by product group.
eg
Variable Set Products
Product Id - ATeam Scoped to Project Group A
Product Id - BTeam Scoped to Project Group BProject Group A
- Proj A1
- Proj A2Project Group B
- Proj B1
- Proj B2Currently we have to override the ProductID in every project in Project Group B which sometimes…
2 votes -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
15 votes -
Add more regional support to Octopus Cloud
Octopus Cloud is presently limited to three Azure regions (West US 2, West Europe, Australia East).
Strict data sovereignty rules for some customers may mean that Octopus Cloud is currently not a viable solution.It would be good if more regions were supported by Octopus Cloud - specifically UK West and/or UK South.
Also - how does Octopus handle high availability and fault tolerance if limited to only one region?
2 votes -
Deploy a Release Step - Task Summary View
We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.
When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.
1 vote -
Support for High Priority Deployments/Tasks
Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
This is not possible now, the only solution now is to cancel all the existing tasks.55 votes -
Add support for SVN (subversion) VCS commit information
After pushing build information from a TeamCity project that was building some code from SVN (subversion) version control system, I noticed that while the package in octopus did have the commit section filled out as expected, the commits were NOT there when creating a release with that package. This meant that we couldn't automatically generate the release notes based on commit messages. I contacted octopus support and we eventually figured out that SVN is not supported.
3 votes -
Disable the 'Deploy' button whilst filters are being refreshed and affected tenants loaded
Whilst in the deployment screen, the 'Deploy' button should be disabled whilst filters are being refreshed and affected tenants loaded.
With the current functionality, it's very easy for a user to add a tag filter and not realise that additional tenants have been included, but are not yet visible in the 'Preview and Customize' section. The loading bar at the top of the box is subtle and easy to miss.
Once affected tenants have been refreshed, the button should be enabled again.
8 votes -
Tenant "overview" page is not intuitive
I find that the most common task performed on tenants is modification of tenant variables. However, I feel that the UI does not support this task very well.
I find that once I click through on the tenant, my next step is to click on the project in which I wish to set variables for which does not result in the expected action (it takes you to the project instead).
My recommendation is that the tenant variables becomes the landing page for tenants and the project administration for the tenant could become a secondary page (or perhaps it could even…
1 vote -
Include description field for project and library set variables similar to project template variables
It would be helpful to have a description field for variables in a project or in library set variables. I know the idea of having 'descriptive variables' usually solves this issue but sometimes across teams it doesn't always happen.
To save screen space it could be a descriptor you enter when making the variable then when you mouse over the variable it shows the information descriptor.
5 votes