Help us improve Gearset
We love getting feedback from our users on how we can make Gearset even better. Post your ideas for improvements, new features, and bug fixes alike, and vote for others – let us know what’s important to you.
167 results found
-
Run only apex test thats related to the Pull request for Validate pull requests targeting the source branch
When we check Validate pull requests targeting the source branch for the Pull request , it runs all the test class irrespective of the package content that being pushed.
It should not run any test class if pushed metadata is only configuration.
It should run only test class if pushed metadata ha class.1 vote -
Automatically identify and run unit tests for deployed classes
When deploying, we have standard options for running tests. It would be great, if we have an option for "auto-specified tests" where Gearset would automatically find test classes for classed being deployed.
It can be done that in Setup, the team will define what type of extension the test classes has and then Gearset would use that key to find matching test classes.
E.g. we have the class "AccountServices" and we have developed a standard set that the test class has extension "Test", so "AccountServicesTest". In the Gearset setup we would set the variable for tests to "Test".1 vote -
Empty cache during meta deployment process
Before you deploy but after you start the process it should be possible to refresh / empty cache to make sure that any updates to the meta data in either source or target are updated.
3 votes -
CI/CV job archiving
Create a mechanism by which CI and CV jobs can be archived, but not deleted. Sometimes there is a job that is not used, but the history needs to be kept for some period of time.
2 votes -
Add ability to clone deployment CI job to validation-only CI job
This would save us time duplicating regex statements for the new job
6 votes -
CI Job History - Show what CI runs were manual and who triggered the manual run
It's nice that the CI job history shows the source commit link for the auto triggered deployments from Github merges, but for visibility and transparency it would also be good for users to see when a job was triggered from a manual run and what users ran it.
4 votes -
Gearset should control the order of deployment for Report Types, Reports and Dashboards
Dashboards require Reports, and Reports require Report Types. Yet when I attempt to deploy a group of components that comprises all of the necessary components, I'm hit with errors that the required components don't exist <yet>. That shouldn't happen. This is going to <artificially> require me to do multiple deployments. :(
3 votes -
Allow CI jobs to validate PRs of a branch into Separate Scratch Orgs
Currently CI jobs can only validate PRs into a regular org. So if you have multiple PRs raised to that branch then you have to wait as they each run one after the other. If we could validate into separate Scratch Orgs instead then all the PR validations could run in parallel and it would speed up validation
6 votes -
Allow Source to choose multiple Branch for CICD Validate/Deploy
when choosing source as GitHub it allows user to choose feature/*** which allows every commit on branch name starts feature will trigger the CICD
2 votes -
Deploy on pull request creation
Currently is supported only validation on pull request creation. It would be great if we can also do deployment on pull request creation, not only on merge.
2 votes -
Control When Tests are Ran Based on Metadata type
It would be nice to control when we want tests to run based on the type of changes in the triggering event for CI. Something like only run test classes on update of Apex Classes, Flows, Workflows, and Objects.
This is a bit of a patch for not having test classes fully optimized but would be helpful with orgs who have lots of profile and layout changes.3 votes -
Don't auto-select all tests when choosing "Select which tests to run"
When selecting "Select which tests to run" Gearset shows the tests included in the comparison first, but the moment all other tests are loaded, everything is selected.
When choosing this option, the tests included in the comparison should stay on top and selected, and the rest of the test should be added alphabetically but UNSELECTED.
If I'm choosing this option, I probably only want to run some tests. I think it would be much easier this way. Usually you need to run the tests included in the comparison and maybe one or two more.
1 vote -
Change Data Capture
When installing a Integration Platform you have to enable the Change Data Capture in order for the platform to receive notifications on changes. At the moment updates under Setup/Integrations/Change Data Capture can not be deployed by Gearset :-(.
1 vote -
Exclude the subcomponents of the parent Workflow metadata and also exclude list views from custom objects
I want to exclude outbound messages from workflows as we will have different urls in different sandboxes. Same with list views we want to exclude them from custom objects so that we can use CI using gearset for deployments
1 vote -
Cloning deployments: add namespace option
If you are using Gearset to develop for a 1GP managed package:
Your deploys between VCS and dev orgs/scratch orgs DON'T use namespace in the metadata filter
Your deploy from VCS to Packaging org MUST USE namespace in the metadata filter - otherwise, everything in the difference viewer appears as NEW rather than CHANGED (if truly just edited during dev cycle)
So, when cloning a deployment, one should have the option to add the namespace to the clone dialog.
Without this, one has to repeat the Compare step thus losing the benefit of what you had enumerated in a prior…
1 vote -
Automatic retry for Unknown Error in scratch org creation
When creating a new scratch org from either the Gearset UX or via a CI job, one often gets the Unknown Error message
Gearset should attempt to retry this error as often, a simple retry works. This is especially important for CI jobs which should not have to be attended to manually.
Of course, the better solution is to not get this error at all
2 votes -
Choose Delete action per Metadata Type for CI jobs
In the past we had troubles deploying reports via CI, they were not showing/deploying, the workaround was to enable the filter to include all reports. This works to solve that, but now I am looking at including more into the repo and start using delete actions in the CI jobs as well. The downside is that because we have to have all reports in the filter, the CI job will delete reports created by users in non-private folders. A freedom we want to give certain users in Production.
What would be an epic enhancement (and solve this challenge) is if…
27 votes -
Load Balancer for CI validation
would be nice to have possibility to configure 1 source (git branch), but multiple targets (sandbox), so gearset would have some "load balancer", which would distribute the validations into sandboxes, which are not busy. Its taking too much time from developers to wait for their validations to finish.
4 votes -
Move Package Contents to Left Column on Deployment Screen
On the "Summary of Items to deploy" page, the items in the deployment show in the 3rd column. So when you go to choose tests, you can't see what's in your package. Makes it very easy to miss a test.
Illustration: https://imgur.com/a/wbZOeiZ
1 vote -
Allow setting the default testing method for deployments
I want to enforce that any deployment into a UAT sandbox runs all the tests. The standard Default option runs no tests since it's a sandbox. I have to manually choose the "Run Only my Tests" Option every time I deploy to that sandbox. I would like to be able to have that option selected by default
2 votes
- Don't see your idea?