Skip to content

Settings and activity

4 results found

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

    Mark Hatton supported this idea  · 
  2. 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

    Mark Hatton supported this idea  · 
  3. 55 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

    An error occurred while saving the comment
    Mark Hatton commented  · 

    We run in to this problem all the time. We have a project that must be deployed to production on demand as an AWS auto-scaling group adds nodes. If we have another project doing a large tenanted deployment (similar to @bastiaan ~200 tenants at 5-10 minutes each, for a total of about 2h45m for a full deployment), we are unable to scale our API layer until all the deployments finish! It's horrible because you're powerless to do anything to override it.

    Ideally being able to set a deployment priority at a project/environment combo level would be ideal, but even being able to manually reorder the queue would be a major step forwards to get us out of trouble sometimes!

    Mark Hatton supported this idea  · 
  4. 215 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

    Mark Hatton supported this idea  ·