Skip to content

Tyler

My feedback

6 results found

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Tyler commented  · 

    I second this suggestion.

    We have a lot of CI jobs and they're connected to specific branches in our repo. When you expand a job, you can see Pull Requests currently targeting that specific branch that the CI job will run on when merged.

    It would be great to have a level above the CI job with a similar functionality. We have a lot of CI jobs for different customers of ours, so being able to lump them into a custom category would be awesome.

    Also, being able to lump production vs development into categories would be great.

    So I could say Customer X > Production > and see their 2 production CI jobs we have.
    Or Customer Y > Development > and see the 20 dev jobs
    etc...

    I know we have the filter, which is very nice, but being able to have them in visibly separated on the page would be very useful if we didn't want to filter out all of the other ones. I utilize many different CI jobs regularly, and it's cumbersome needing to filter back and forth to find what I want.

    Tyler 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler shared this idea  · 
  4. 2 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Tyler commented  · 

    If a Validation CI Job would create a Validated Package, we could use that validated package to schedule deployments.
    I could even see the Validated package only being created for the top level CI comparison, not for each of the PRs that are getting validated (if they are).

    Tyler supported this idea  · 
  5. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler shared this idea  · 
  6. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Tyler supported this idea  · 
    An error occurred while saving the comment
    Tyler commented  · 

    To add to the above, if a handful of the PRs all fail validation, there is no way for us to link the failed validations to the Gearset Job that points us to the PR. Just a handful of failed validations for various reasons in the SF Validation Dashboard.

    Tyler shared this idea  · 

Feedback and Knowledge Base