shreyas-girjapure / salesforce-pipeline Goto Github PK

• Print Heads of git logs
  git log --oneline -n 3
  prints the last 3 logs and heads

• Get names of the files changed between the heads
  git --no-pager diff --name-status $BEFORE $AFTER

• Command to create a zip for package
  sfdx force:mdapi:retrieve -r ./mdAPIZip -u IDFC-dev -k force-app\main\default\manifest\package.xml

• Validate Package
  sfdx force:source:deploy -x force-app\main\default\manifest\package.xml -c

• Deploy component
  sfdx force:source:deploy -x force-app\main\default\manifest\package.xml

• Run specified Tests
  sfdx force:source:deploy -x force-app\main\default\manifest\package.xml -l RunSpecifiedTests -r "AssetAndLiabilityTrigger_Test,AssetLiabilityTriggerHelper_Test" -c

• Deployment report
  sfdx force:source:deploy:report --verbose

• Deployment with ID
  sfdx force:source:deploy:report --verbose -i 0Af72000004ajad

• Storing org info in json file
  sfdx force:org:display -u shreyasHome --verbose --json > authFile.json

• Run tests and output to some directory
  sfdx force:apex:test:run -c -r tap -d ./tests/apex -w 20 -v -l RunLocalTests

• Run Test for specified names
  sfdx force:apex:test:run -c -r human -d ./tests/apex -w 20 -v -l RunSpecifiedTests -n "TemperatureConverterTest,CalculatorClassTest"

• Admins changes can be pulled by
  sfdx force:source:pull -f

Currently just a single irrelevant push or pull to the branch is triggering deployment of whole source folder.

This will help in keeping the code clean.
We can create our own actions this way lots of possibilities.

This slightly depends on two issues

1. Running local server problem.
2. Prettier formatting on apex class

• Delta Deploy
• Git Hub Context variables to be used in actions
• Just Another Dang How to Channel Delta Deploy
• Github Branching
• Coding with force Circle CI
• Repository referred for good implementation
  There are really good implementations available in this repository S/O to this guy. I really liked the project structure and keeping components separate from each other also there are various use cases and advance implementations available. Do checkout this repository
• Create an Action

Currently everything is implemented and tested for push events.
For concrete changes have been made for pull requests. Need to check runs for PRs as well.

Implement code modularizations if needed for PR and Push events separately

Currently all org tests are running ,
This is causing delays in deployments. By specifying the tests OR making pipeline smart we can make this more performant.

Note :
When designing the test classes if there is some org wide pattern for naming the classes then we can make our code smart to detect test classes for changed class.

Deploy only the diff or Delta not the whole source code.
currently whole source folder is retrieved and pushed for deployment.

This is pretty self explanatory.
Ability to send mails/notification via github actions

Currently changes are directly deployed to master.

We need a branching strategy to provide safe and quick deployments.

Here scale of the project and teams working on it are important factors to be considered.

Prettier is providing with formatting errors when tries to format .cls files with bad indentation.
Same is problem with prettier installing on virtual platform

Plan was to add prettier formatting support so that all of the code remains in sync

problem with the prettier is that it adds a extra space in mostly xml ymls and line break at the end of js 

this causes problems in case of scheduled refresh of branch with source code.

Currently all of the problem causing files have been removed 

Also .cls files are excluded from the formatting , Prettier is causing issues with formatting of those files.

Steps to reproduce

1. Create new class
2. Commit and Push
3. Check if it has been deployed

This is to make code make more configurable and to make it more data driven.