AdminOctopus Developer (Software Engineer, Octopus Deploy)

My feedback

  1. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    There appears to be some confusion as to what should be added where since using values files are the recommended way to use helm.
    Could you please drop us a line at support@octopus.com so we can more easily continue this conversation and determine what feature is lacking.

    The ability to perform variable replacement on values files is already supported on the helm step. Rather than using Octopus to perform variable replacement directly on templates, its recommended that you use values files. Is this currently not working?

  2. 809 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    We have had to pause development of this feature while we focus on finishing work on spaces. We expect to get back to complete this work sometime in the next quarter.

    @ChrisCamburn we are looking at adding support to expose package selection on step templates out to the consuming project so that users no longer need to rely on variables to get different package values into a step template.
    https://github.com/OctopusDeploy/Issues/issues/4270
    Would this solve your problem?

  3. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    We currently expose the sha256 hash through the HTTP header through the MSI download link.
    The header is `x-amz-meta-sha256` alongside the existing `x-amx-meta-md5`. Although this is not immediately provided through the portal this will provide the required information.

    e.g for
    https://download.octopusdeploy.com/octopus/Octopus.2018.6.2-x64.msi
    the HTTP headers

    x-amz-meta-sha256: B371FB0775867E1CBE29DA977F4FDCABBA6E58855EBEF15D13FB2998AF520B3C
    and
    x-amz-meta-md5: 7C44113ABB87335356937247862CEC7D

    are both provided

  4. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    We have added some new features in the 2018.5 release for dynamic Azure targets that may support this.
    Please see the following pages for more information:
    - https://octopus.com/blog/paas-targets
    - https://octopus.com/blog/octopus-release-2018.5
    - https://octopus.com/docs/infrastructure/dynamic-infrastructure

  5. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    The task list currently (as of 4.0) provides the ability to view all running tasks. Does this feature meet your requirements?

  6. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Hi @Grendizr
    Octostache, the templating library that is used, is fully open source so we are happy to receive pull requests
    https://github.com/OctopusDeploy/Octostache

  7. 33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  5 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    We have some changes in the works that may fit your requirements.
    The new concept called Spaces (https://github.com/OctopusDeploy/Specs/blob/master/Spaces/index.md) will allow users to partition their projects. Those that share the same actual environments (which is very common, think about things like micro services or interdependent applications) can be organised together. At the same time other projects which may still have something called a "Production" environment, may in the real world be actually completely different environments.

    While this feature is largely target towards providing ways to help organize how large teams use Octopus, I could see this approach as providing a potential way to help segment your projects if this is a concern for you.

  8. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    AdminOctopus Developer (Software Engineer, Octopus Deploy) shared this idea  · 
  9. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for getting in touch. For bugs like this we find that a better channel is to log them via our dedicated [support forum](https://help.octopus.com/) or support@octopus.com

    Could you please provide more details via the support channel with details about which version of Octopus you are using along with any information that may help us to reproduce this issue like what page you were on (I'm assuming it's the dashboard based on the network screenshot) and further details about what the error messages were that you are seeing. Which calls in particular feel slow?

  11. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    @Scott are you aware that you can already configure your dashboard to only show specific projects and environments?

  12. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Geert, Project variables can already be scoped to steps.
    https://octopus.com/docs/deployment-process/variables/scoping-variables#Scopingvariables-Scopespecificity
    Is this something not working for you?

  13. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    Is there a concern or problem using SQL Server? Supporting other RDBMS would add a load of additional development, maintenance and support overheads so would be an unlikely option unless there are important issues. If it is a problem with installing and managing this peice of infrastructure is it possible to just use Microsoft Azure SQL Database or AWS RDS SQL Database?
    https://octopus.com/docs/installation/sql-server-database-requirements#SQLServerDatabaseRequirements-Supportedversionsandeditions

  14. 636 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. 32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Our recommended approach for this is to have a single transform file in your solution, for example web.octopus.config, which contains placeholders for octopus variables, e.g. #{ConnectionString}.

    During deployment, you run variable-substitution on that transform file, and then use it to perform the transform.

    This achieves the goals of:
    - Storing variables in Octopus
    - Your solution doesn't have to know about environments
    - But knowledge of the actual structure of the config file is all contained in your solution.

  16. 101 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    @Thomas

    Could you expand on the use-case. I assume you would not be using variable substitution, scripts or config transforms on the files in that folder? Do you use Custom Installation directories?

    A small correction, the path is extracted to `C:\Octopus\Applications\tenant1\Production\packageName\v_0.0.1` (ie packageName instead of projectName).

    Once the files are extracted we use that folder to run the scripts for the other features (eg IIS configuration, config transform, pre/post scripts).

    Could you use the transfer package step and then a script step to conditionally unpack the package? You could also have a script step at the start that figures out if you have to do anything, then sets an output variable that is used to conditionally run the next two steps.

  17. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    In testing, it appears that deploying to RaspberryPI via a SSH target and using mono to run Calamari seemed to work just fine. Has this caused problems?

  18. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Is there any reason that our existing proxy support does not meet these needs?
    https://octopus.com/docs/infrastructure/windows-targets/proxy-support

  20. 45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    It is hard to decide how such a feature would be able to be natively implemented. The best suggestion would be for users to bundle an uninstall.ps1 script (to ensure that the uninstall process is tied to the version deployed) then use the Octopus.Tentacle.Package.PreviousInstallDirectory variable in a script before the "new" deployment step to access and invoke that script on subsequent deployments.

    How would Octopus be expected to uninstall if for example roles are removed from a machine? We then no longer have any way of knowing what machines were involved in that release or if it should be our responsibility to now try and connect to something that has explicitly been changed to no longer be part of that deployment.

← Previous 1 3

Feedback and Knowledge Base