Skip to content

Settings and activity

6 results found

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

    Ryan Adler supported this idea  · 
  2. 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

    Ryan Adler shared this idea  · 
  3. 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

    Ryan Adler shared this idea  · 
  4. 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

    An error occurred while saving the comment
    Ryan Adler commented  · 

    In fact, all that needs to be done is to enable multiple full installations of tentacles on a server, in different directories. These can then be added to cluster resources.

    An error occurred while saving the comment
  5. 13 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
    Ryan Adler commented  · 

    I second this - we also have time periods where workload is high for our apps, and users would like to have a rollout freeze to prevent possible issues.

  6. 33 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
    Ryan Adler commented  · 

    In this case, I would just give Child Steps a Start Trigger field, just like their parent's settings. The setting would allow child steps of a single top-level step to run in parallel with each other. Then, depending on the setting of the next top-level step, its children could also run in parallel with the first group of children.

    For example for the following structure:
    Step 1
    Step 1.1
    Step 1.2
    Step 2
    Step 2.1
    Step 2.2

    If Step 1.2 has a start trigger which lets it run in parallel, it would run at the same time as Step 1.1.
    If Step 2 is set to wait for Step 1 to finish, it will wait until all the children are done.
    If Step 2 is set to run in parallel with Step 1, then I would expect Step 2.1 to be able to run at the same time as Steps 1.1 and 1.2.
    Likewise, if Step 2.2 is set to run in parallel, it could run at the same time as Steps 1.1 and 1.2.
    If Step 2.2 is set to wait for the previous step to finish, it would wait for Step 2.1 to finish before running.

    To summarize, the Child Step Trigger setting would affect whether or not children of the same step can run together, while the trigger setting on the parent would determine if the children could start in parallel of another top-level step.

    An error occurred while saving the comment
    Ryan Adler commented  · 

    Note that also, without this feature, it is not possible to take advantage of rolling deployments and parallel steps at the same time.