Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. I'd like to capture some additional fields along side every release.

    For example, every release of my project, should have a corresponding:

    • Team City Build Number
    • Team City Build Type Id
    • Team City Build Id

    At the time of creating a release in Octopus, if done through the octopus UI - these values would be prompted for.

    If done through Octo.exe then the create release command should have the ability to set these release specific property values.

    The reason this is useful is because:

    1. The Octopus Release number no longer has to match the Team City build number in order…
    24 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

    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. If there were a mechanism for serving artifact files, we could
    (i) run some lightweight javascript to do things like load-on-demand
    (ii) provide a more integrated user experience (opening a file from downloads feels clunky)

    The mechanism could be to show artifact files in tabs in the approval step and completed release summary pages. There could be an 'add artifact tab' option in settings, which allowed you to name the tab and specifiy the artifact file to be displayed.

    TeamCity allows you to serve artifacts from tabs in build results through project config options - https://confluence.jetbrains.com/display/TCD9/Including+Third-Party+Reports+in+the+Build+Results

    6 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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We are using TeamCity as a CI engine, and trigggering OD from there. Once we have triggered a deployment, we want to run tests against that environment.

    At present, we need to have the required configuration settings in both OD and the code to allow the tests to point to this environment.

    We can currently use the api to get the variable values from a release, and duplicate the code from Octopus to update a config file, however this will be a maintenance nightmare as Octopus evolves.

    It would be great if there was a way to use Octopus to…

    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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Currently octopack supports either msbuild override, AssemblyInformationalVersion, or AssemblyVersion and does so in a predefined way. It would be useful if this selection was customisable/controllable.
    E.g. If AssemblyInformationalVersion (which supports string) does not conform to a valid Major.Minor.Patch.Build scheme I would like to specify either AssemblyFileVersion or AssemblyVersion.

    I cannot specify the value of these to octopack via msbuild arguments because the version scheme itself is controlled/applied by a TFS pre-build script.

    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

    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. An easy way to attach deployment artifacts would complement this feature very well.

    107 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

    19 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Would it be possible to update the releasenotesfile switch on octo.exe to allow for HTML files? My build server currently creates an html report for the releasenotes, which i would like to attached to the release via the "octo.exe -releasenotesfile" switch but it always displays an blank section. If I attach a plain text file is works, but I would like to be able to format the report.

    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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Sorry if this has already been discussed.

    I was creating some powershell modules and I noticed there is no option to set dependencies on other modules.
    This would be great. Right now I am using the description to track the dependencies, but is not ideal.

    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

    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Azure Web Sites extensions: http://azure.microsoft.com/blog/2014/06/20/azure-web-sites-extensions/

    How amazing would it be if you could add in an extension to your Azure Web Site that can connect to a OctopusDeploy server and register that website in a particular envionment with a particular role and have NuGet packages deployed to it?

    It would be a much nicer ootb experience then the current Azure Web Sites Web Deploy library item (which is definitely awesome, but it's not very seamless).

    12 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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We currently want to set features like the number of worker processes. It would be good to be able to set these up from Octopus instead of powershell.

    21 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

    5 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Currently, OtcoPack considers a project a web application if a web.config file is found in its root. My stand-alone ServiceStack service project needs to have such a file when working with Razor support to enable intellisense support in VS. The web.config is never deployed however but OctoPack now deploys the project in web-style. That is, copying all binaries to the 'bin' sub directory while they should really go into the root. See https://github.com/OctopusDeploy/OctoPack/blob/fa2bbe0ce4b489316e090bf35f4d7d74d1d3a92a/source/OctoPack.Tasks/CreateOctoPackPackage.cs#L463

    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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 3 5 Next →
  • Don't see your idea?