Richard
My feedback
3 results found
-
13 votes7 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Richard
supported this idea
·
-
2 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment Richard
supported this idea
·
-
16 votes5 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Richard
supported this idea
·
Separate project json file definitions are a must for automated build jobs outside of gearset. This is to allow simple build of the package without dependencies being introduced on other metadata that appears in the same repo but in a different folder location. When this is a mono repo where Gearset is used as the CI and deployment tooling for unmanaged packaged metadata then Gearset fails with the presence of more than one project json file.