tfbryan

My feedback

  1. 1 vote
    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 →
    tfbryan shared this idea  · 
  2. 23 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 →
    tfbryan supported this idea  · 
  3. 16 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 →
    tfbryan commented  · 

    Here's what I did >>> In the child projects, set up a trigger to auto-release. Then when you go to create a release from the project that contains the "Deploy a Release" step, it will have all the latest releases available.

  4. 8 votes
    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 →
    tfbryan shared this idea  · 
  5. 120 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  General » Integration  ·  Flag idea as inappropriate…  ·  Admin →
    tfbryan supported this idea  · 
  6. 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 →
    tfbryan commented  · 

    Being able to programmatically tell the Parent deployment which target machine it should deploy to would be huge. For instance, we need to deploy several packages and orchestrate them within a rolling deployment. Currently, I don't see that there is any way to do that with Release A Deploy steps.

    tfbryan supported this idea  · 

Feedback and Knowledge Base