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.
195 results found
-
Add option to provide exact time in case automatic deployment
We need to set exact time for automatic deployment. We need this option for example for night releases for specific client. This is important for international clients that works in different time zones
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 -
Add an option to disable Problem Analysis for CI
When running CI jobs, we can create a problem analysis template to control what potential problems can block a deployment.
For deployments from SF orgs to Git, many of the problems being analysed are just irrelevant (e.g. users don't exist in the target, because the target is not Salesforce).
Although some options can be switched off via templates, the list is not comprehensive. So, it would be great to have an option to switch off everything, or a built-in template of "no analysis".
When production is the source of truth, we just want all the metadata to get copied into…
1 vote -
Make metadata filters easier to use when you want to "include all except X,Y"
For CI jobs, it is not uncommon that you want to include all elements of a given custom metadata type except specific elements
Today, you need to have two entries - an include all (".*") expression and an exclude expression. For users who are not regex savvy, this is too complicated.
We should have "All", "Named", and "All except Named" at the top level so simple check boxes can be used.
This is particularly useful for CI jobs (whose purpose is to sync VCS w/ org) - you want to sync most everything except a few items - like Sites…
1 vote -
Add the ability to order/chain overnight jobs
Gearset offers various automated jobs that run overnight e.g. Org Monitoring Snapshots, CI Jobs, Unit Test Runs.
it would be great to be able to set an ordering on how those run for any particular org. For example, a natural order for the night jobs may be:
- Monitoring Snapshot
- CI run
- Unit testing
This means we have a backup before making any potential CI changes and the unit tests show the results after CI. It would also allow us to make sure that the jobs don't clash.
Ideally, we'd be able to do this without just specifying exact times to…
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 -
Ability to differentiate between scheduled metadata deployments from validated packages and non validated packages
Under Deployment History
All scheduled packages should appear. This is not the case today, validated packages that have been scheduled appear under validated packages with a Scheduled Date but not under Deployment History
Scheduled packages should have a link to the appropriate Validated package if any.
1 vote -
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 -
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 -
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 -
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.
3 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 -
For failed CI job runs, develop a way update to the job status
When for whatever reason, jobs can get job stuck in status "Deploying".
The real deployment task is already successfully finished in the org, so I would expect that the status of the CI job would be "Succeeded".
I was assured that in 24hrs the status of the job will automatically reset, but can we have also a way to force an update to the CI job manually?
Note: The "Cancel running CI job" button is visible and clickable, but doesn't do anything with this stuck CI job.
1 vote -
Run all tests only when have apex classes in the package
Hello,
I want suggest an option to avoid run unit tests when no have apex class in the package.
And run all tests when have any apex class in the package.1 vote -
Publish dynamic data with Outgoing Webhook in CI deployment jobs
As of now we are able to send only static text as a part of outgoing payload in CI Integration jobs. We want this data to be dynamic for each deployment.
For example: We need to send the information like (JIRA User Story number, GIT commit hashes and descriptions from the pull requests being merged, etc.)
This will allow us to publish information of successful deployments to external system.20 votes -
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 -
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 -
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 -
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
- Don't see your idea?