Skip to content

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1458 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
  2. When collapsing a log entry/header for a task it would be great if the total duration was displayed. That way it would be easy to spot slow tasks in a full deployment.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  3. We have created a deploy script that we use as standard on all of our projects. However we do have to include it in all of our projects. The only difference is the variables we pass to each project.

    It would be great if deploy.ps1 could live on the tentacle and execute that if the project doesn't have one. Or possibly chain them, tentacle executes its deploy.ps1 (if one exists - maybe a project option to skip it), then execute the project level deploy.ps1 (if one exists).

    This would save us time having to include it (ok its not a…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  4. I have different applications that deploy to different sets of servers. I could create unique environments to handle the separation but it could get ugly pretty quick. If a project group was tied to a set of environments it would make it easier to know what environments apply to that project and prevent me from selecting the wrong environment to deploy to.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  6. Add a concept of release quality. One should be able to define (per-project) a number of quality dimensions (e.g. regarding unit tests, performance tests etc.). Values in each dimension should have absolute order. Than, for each environment one should be able to define a minimum quality level for each dimension that a release need to have in order to be deployable e.g. for UAT environment both unit and integration tests need to pass and for PROD also the performance tests need to be OK. The build quality would be editable via UI (e.g. by a QA person) and via the…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  7. On the dashboard, when hovering over a successful build an arrow should appear next to it with the word 'Promote' clicking this button should start the deployment to the next environment in the chain.

    On the dashboard, when OD detects there is a new version available on the nuget feeds, a small + symbol should appear next to the project name, clicking this should take you to the create release screen.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
  9. Enable double click or something like that on a Tentacle machine in the environment overview. When you click/doubleclick/other then adownload is started with a preconfigured rdp file.
    Just like you do on amazon.
    This way its easy to open a connection to a specific tentacle and octopus only has to create a downloadable rpd file, with server name and possible pre filled domain/user,
    VERY nice feature for handling your servers and apps :)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  10. Add support for custom pages or widgets that can be added to the Octopus Server installation along with custom fields that can be assigned to Project and Release. An example would be a NUnit widget that could use API to fetch NUnit test results artifact and format it nicely on release page. Other example could be storing 'build quality' property along each release. The value would be updated e.g. by the build server after executing unit tests or integration tests or a QA person after doing some exploratory testing

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
  12. When the tentacle service shuts down, the polling tentacle would change the machine.isdisabled = true. When the service starts it would set the isdisabled=false. this allows cloud based infrastructure to dynamically turn off machines without having the deployments fail because the machine is turned off.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. I want to be able to deploy Nuget packages to a Nuget Feed directly from the Octopus Server - I dont want to have to publish to a server that has a tentacle on it then run a script to deploy the package.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  14. It would be nice to be able to run Octo.exe update-self or something like that to get the latest Octo.exe isntead of going to the website and downloading the latest version.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. In the Cloud configuration file for Azure deployments you can specify VirtualNetworkSite to determine which network the role will be deployed to. It would be great to be able to specify this in Octopus.

    An alternative is to specify which service configuration (default Cloud) to use for the deployment/step.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  16. The latest assembled release should feature more prominently on the releases page, at present it is at the top of the recent release list, but it does not jump out at you, The latest release should appear to the left of the currently released versions. when you click it you should be taken to the deploy page.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
  18. Add XmlPoke functionality for setting various config values.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →
  19. The implementation of the 1.6 TeamCity plugin just has it as an extra setting under VisualStudio build step. It would be great if we could have this as a seperate build step.

    We would like to be able to build our project, run tests and if all tests fail then package and publish to TeamCity's feed to Octopus to detect.

    This isn't to big of an issue because TeamCity won't automatically deploy as it stands now. However if a user logs into Octopus and manually creates a release, they can select the potentially broken artifacts.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Admin →
  20. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Admin →