Saul Guttman

My feedback

  1. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)

    We do multiple deployments a day, this is very challenging to do in a services world, especially for the cloud part: the portal and multiple other parts of the online service can change and be redeployed dozens of times each day, every day, on a typical week when developers check in new code, this goes thru a bunch of automated validation, and then gets pushed out.
    We have ability to show/hide new features to selected tenants/workspaces – but there are a lot of teams that independently contribute to the portal and system for various scenarios, and check in and deploy their changes independently thru automated workflows.

    We intentionally go ‘slower’ with the Intelligence Packs – because we know that they can affect on-premises. Those are generally pushed out at a slower cadence, but can still happen a few different times in the same week; the deployment mechanisms are similar, but…

    An error occurred while saving the comment
    Saul Guttman commented  · 

    I like what this tool/service provides but I do not think that this tool/service can really be called enterprise ready if there is no release management. I have had two outages as a result of AOI running on production servers and I simply had to remove the service from all hosts in my environment. In my opinion the risk outweighs the benefit.

    Saul Guttman supported this idea  · 
  2. 50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Saul Guttman shared this idea  · 

Feedback and Knowledge Base