Setting up a local repository in VS Code
Confluence: https://sydneyuni.atlassian.net/wiki/spaces/SNGL/pages/2715779242/Salesforce+Continuous+Integration+and+Continuous+Deployment+CI-CD#Initial-set-up
...
...
Resolving merge conflicts
Expand |
---|
title | Merge conflict resolution steps |
---|
|
Checkout to the source branch. Make sure to take note of your changes that must be merged and deployed. Run the Git fetch command. From the Terminal, run the Git checkout command to copy the contents of a file from the target branch: Code Block |
---|
git checkout <target_branch> -- <file_path>
git checkout origin/master -- 'force-app\main\default\classes\SampleClass.cls' |
The file will now be the same as what is in the target branch, and your changes will be overwritten. Commit and push the staged changes. Create a pull request, merging the source branch to the target branch. This pull request should not contain your actual changes, and will only contain changes found in the target branch but not in the source branch. With the file still open, manually add your changes. Commit and push to the remote branch. Create a second pull request, merging the source branch to the target branch. This pull request will contain your actual changes, but with no more merge conflicts.
|
...
Revert a merged commit
Expand |
---|
title | Reverting a merge commit |
---|
|
Create a new, temporary branch based from the branch you want to revert a merge commit from, e.g., TAP-1250-RevertFromMaster based from origin/master Get the Commit ID of the merge commit you will revert, e.g., 294229cf
Image AddedMake sure you are checked out to the temporary branch. From Terminal, type command:
Code Block |
---|
git revert <commit id> -m 1
git revert 294229cf -m 1 |
Commit the changes in the temporary branch, and then publish branch From the temporary branch, create a pull request to the target branch, e.g., TAP-1250-RevertFromMaster to origin/master Once pipelines are successful and PR is approved, merge to target branch
|
...
Adding new project to CI/CD pipelines
Confluence: Adding new project to CICD pipelines
...
Downstream deployments
Expand |
---|
title | Downstream deployment process |
---|
|
This process is done after PROD deployments to sync sit and uat branches with master , and uses a “no-commit” branch that is based from master . Use the branch: ALL-noCommitFromMaster . Make sure to rebase the no-commit branch by running a Git pull command:
Code Block |
---|
git pull origin master |
Push the commits. Create a pull request for merging ALL-noCommitFromMaster to sit , and another pull request to merge the same branch to uat .
|
...
Useful SFDX commands
Code Block |
---|
// validate multiple files using package.xml
sfdx force:source:deploy -c -x manifest/package.xml -l NoTestRun
// validate a single file
sfdx force:source:deploy -c -p 'force-app\main\default\classes\SampleClass.cls' -l NoTestRun
// retrieve multiple files using package.xml
sfdx force:source:retrieve -x manifest/package.xml
// retrieve a single file
sfdx force:source:retrieve -p 'force-app\main\default\classes\SampleClass.cls' |