Sam “Betty” McKoy

My feedback

  1. 8 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 →
    Sam “Betty” McKoy shared this idea  · 
  2. 162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy commented  · 

    Found a work around - powershell step to find the thumbprint.

    $thumbprint = get-childitem cert:\localmachine\webhosting -Recurse | where { $_.subject.StartsWith("CN=blah.blah") } | where { $_.notafter -gt (get-date) } | select -expandproperty Thumbprint

    Set-OctopusVariable -name "ThumbPrint" -value "$thumbprint"

    Sam “Betty” McKoy commented  · 

    Instead of specific support for Letsencrypt maybe it makes sense to be able to bind certificates via name instead of just thumbprint? That way we don't need to update octopus whenever we get new certs, no matter where the cert is sourced from.

    Sam “Betty” McKoy supported this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy commented  · 

    Events could allow for interesting things permissions wise - eg adding manual intervention without the ability for developers to remove it from projects.

    Sam “Betty” McKoy commented  · 

    other ideas that might work
    * nestable global steps (currently we can import shared steps, would be nice if those steps could contain multiple steps)
    * reusable process templates (eg custom like normal or use a predefined process).

    That said some kind of event system could be more powerful, just might not be so clear on what is happening (eg you'd want it somehow visualised in each project so you can figure out why things happen).

  4. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy supported this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy commented  · 

    Option for first deployment only could work too, would also fix some issues.

    Sam “Betty” McKoy commented  · 

    alternative - split the deploy package step out so that individual parts can be scoped to particular environments - not ideal as I really like the idea of being able to verify an environment but would at least allow me to use octopus in a couple more environments.

    Sam “Betty” McKoy shared this idea  · 
  6. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy commented  · 

    maybe ${Octopus.Release.Channel.Tag} and ${Octopus.Release.Channel.Version} could be created when a package matches a version rule?

    Sam “Betty” McKoy shared this idea  · 
  7. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy shared this idea  · 
  8. 146 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy commented  · 

    Potentially custom Triggers (like the release triggers in 3.4)?

    Sam “Betty” McKoy commented  · 

    This would be great for cleaning up after release per branch scenarios.

    Needs to take channels into consideration (probably life cycles/environments in general)

    Also wonder if it makes sense to be a octopus task list instead of script

  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy shared this idea  · 
  10. 124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy supported this idea  · 
    Sam “Betty” McKoy commented  · 

    @peter that would only work for the first environment. If you fixed a bug in that environment then the next one would only see the bugfix note.

    You could have a branch per environment but that basically defeats the point of octopus.

  11. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Sam “Betty” McKoy supported this idea  · 

Feedback and Knowledge Base