165 results found

1. Check for conflicts on CI

   We have a scenario where CI would be useful, but there is a risk of it making destructive changes...

   Orgs in involved are Prod, UAT, Dev.

   Ideal development path would be Dev->UAT->Prod with each deployment using Gearset.

   In the real world, admins make some changes directly in Prod. So, we also need to merge changes back from Prod->UAT to make sure that UAT is a realistic test environment.

   It would be great if we could make a CI connection from Prod->UAT which automatically deploys non-destructive changes, and notifies us if a change cannot be sent to UAT for risk of destroying something that has come in from Dev->UAT.

   It seems like there are a couple of potential options for detecting what might be destructive...

   1. If we are using Gearset to do all the deployments Dev->UAT, then when a potential CI job from Prod->UAT is going to overwrite something that we know from the deployment history to have come from Dev but not been sent to Prod, then this would count as a potentially destructive change.

   2.If the last modified date of the metadata item in UAT is newer than the last time that element was update by a CI job from Prod->UAT, then the change would count as a potentially destructive.

   We have a scenario where CI would be useful, but there is a risk of it making destructive changes...

   Orgs in involved are Prod, UAT, Dev.

   Ideal development path would be Dev->UAT->Prod with each deployment using Gearset.

   In the real world, admins make some changes directly in Prod. So, we also need to merge changes back from Prod->UAT to make sure that UAT is a realistic test environment.

   It would be great if we could make a CI connection from Prod->UAT which automatically deploys non-destructive changes, and notifies us if a change cannot be sent to UAT for risk of… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Give the option of deleting or retaining metadata components that are not within a package.xml - during the CI process
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Filtering by user across the app

   Filter deployment history & automated jobs to only show a specific team member's activity (e.g. mine). With large teams, the history pages can get too busy and makes it difficult to find the results I'm interested in.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. On an unsuccessful validation, allow me to easily retrieve offending test classes so I can re-validate quickly.
   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Filters

   Edit "Existing Saved Filters" on an "Existing CI Job"

   If using a saved filter on CI job, there is no easy to update an existing saved filter from the CI job directly.

   Here is my current workflow:

   Start a new compare and edit / save the filter from there, then going back to the CI job, refreshing filters and reselected the saved filtered.

   If multiple CI jobs are setup it's easy to miss some jobs which are dependent on updated filter.

   Alternative solution - Provide toggle to update all related CI jobs which use the filter.

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployment automation  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close