Jonathan Flatt
My feedback
55 results found
-
3 votes
An error occurred while saving the comment -
3 votes
-
3 votes
-
28 votes
-
6 votes
-
2 votes
An error occurred while saving the comment This would be huge. Honestly should be default Salesforce behavior to ignore these components with a warning, or to have the option.
-
2 votes
-
4 votes
An error occurred while saving the comment At least in bitbucket, loading the repositories on the compare and deploy page takes around 10 seconds. 99% of the time we'll be using only a single repository. Being able to set a default repository and perhaps on the page allow the user to change the repository and only then retrieve the repositories from VCS.
-
3 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
9 votes
-
3 votes
This is currently planned for later this quarter and next.
Users will have the option to:
- Bulk update selected dev sandboxes
- Automate developer sandbox updates; they will be immediately tried as and when ready
If users want to automate dev sandbox sychronization now, they can use CI jobs to deploy changes from their desired source of truth - this comes with some risk of affecting work in progress though.
-
7 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
3 votes
An error occurred while saving the comment Not sure if it would cover OP's use case, but it would be interesting to include 'recently failed tests' to a CI job's test selection heuristics.
-
4 votes
-
3 votes2 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment This would allow us to take advantage of Bitbucket's rate limit increases: https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/ which are only available by using a "workspace, project, repository access tokens for authentication or make requests through programmatic access via a Forge app."
I believe this would alleviate a major pain point we've been experiencing due to being rate limited by bitbucket. These rate limits are hindering our ability to scale up our CI/CD pipeline.
-
9 votes
-
3 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
1 vote
-
82 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
-
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
I have Gearset call out to bitbucket after a successful deployment and publish portals in a bitbucket pipeline using the sf cli. Each org does need to be configured in both the CI job and bitbucket though. It's been working fine as a workaround.