Mike
My feedback
18 results found
-
4 votes
Thanks Mike for submitting your idea.
Gearset's Environment Variables feature already supports partial string replacements, which means you can get Gearset to replace 'sandbox1' bit of the <user> tag value with 'sandbox2', as follows:
Target: Sandbox2
Metadata Type: Platform Event Subscriber Configuration
Item: Any item
Find: sandbox1
Replace with: sandbox2
An error occurred while saving the comment -
2 votes
-
1 vote
-
11 votes
-
16 votes
-
12 votes
An error occurred while saving the comment Agreed! I'd like to be able to rely on the comparisons to only show legitimate differences rather than having to memorize which specific metadata items are always there due only to reordering.
In fact, I'd prefer they be considered identical and suppressed completely, so that the CI jobs don't attempt to deploy them and they don't show in their historical comparisons.
-
5 votes
-
1 vote
-
9 votes
-
2 votes
-
9 votes
-
6 votes
-
7 votes
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
9 votes
-
28 votes
-
4 votes
-
8 votes
Thanks for the suggestion.
When you run a deployment, the deployment success email contains the PDF of the deployment report, as well as a link to your deployment history to view the full information.
For the test/change monitoring emails, what sort of report would you like to see? Would you like to see the full information on tests run or just a summary of key stats?
We don’t currently provide the ability to export PDF reports for our change and test monitoring jobs in the same way as our deployments, but it’s something we’ve been thinking about putting in.
Thanks,
Jason.
@Gearset Team - that only works if the value in source has .sandboxName appended. However, we keep production's value in source, which has nothing after the email address. As such, there's nothing to replace.