Escrever um comentário...
0/9000
AvisoSource Control / Version Control foi arquivado. Para reativar, contacte o proprietário do grupo James Loghry.
Grupo
Source Control / Version Control
Hello All, I am new to Salesforce Devops side and looking for help to know the best & the latest way to set CI environment.
Tools that we are planning to use -
1. Git
2. Bitbucket
3. Jenkins
Note : Scratch orgs can't be used in our case
Any pointers would be really helpful.
Thanks!
Hi All,
I'm using visual studio code for dev and GitLab. I'm trying to get code from git branch, and then connect it to salesforce sandbox and made the required changes, test it and commit to git.
But here when I get code from git, in Visual studio code it's not showing me option to SFDX: Authorize an Org, and if I get source code from sandbox it's not connecting to git repository, is there any way to connect vs code with salesforce sandbox and Git at the same time and do the changes?
Much appereciate any input on this.
Thanks,
Bindu
Hi all,
my colleagues have been trying to deploy report subfolders from GIT to another Sandbox environment. After deployment these subfolders appear as folders but not contained in the report folder.
For example, you have this structure:
Service Reports --> Folder
In the Service Reports folder you have two subfolders 'Service Reports 1' and 'Service Reports 2' subfolders.
On GIT these are being correctly shown as subfolders:
<members>Service_Reports</members> <members>Service_Reports/ServiceReports1</members> <members>Service_Reports/ServiceReports1/Service_Report_within_the_ServiceReports1_subfolder</members>
But once deployed, the subfolders appear as folders and not as subfolders within the Service Reports folder, why?.
Are my colleagues missing something so that report subfolders are not being correctly deployed as such from GIT?
@Salesforce Administrators & Developers @Architect Trailblazers @Who owes me a beer?!? @GIT ADMIN2@Source Control / Version Control(Deleted Group)
2 comentários
Hi @Martin Humpolec, we couldn't find a solution. We just executed a post deployment step, which is to create the subfolders manually in the target environment.