CI/CD Config Home
- package.xml
- destructiveChanges.xml
- Automated sources cleaning
- Source retrieve issues
- All configuration properties
package.xml
A Salesforce CI/CD repository contains a file manifest/package.xml.
- It contains all metadatas that will be deployed by the CI server.
- It is automatically updated when preparing merge requests by command hardis:work:save
Overwrite Management
-
It is highly recommended to configure overwrite management, to avoid to overwrite metadatas that are maintained directly in production on purpose
- Dashboards
- Reports
- Remote site settings
- Named credentials
- ...
Delta deployments
- You can also use delta deployments if your project is big and you have performances issues.
Source retrieve issues
Handle cases when force:source:pull does not retrieve every updated source.
See how to force the retrieve of named sources
destructiveChanges.xml
A Salesforce CI/CD repository contains a file manifest/destructiveChanges.xml.
- It contains all metadatas that will be deleted by the CI server.
- It is automatically updated when preparing merge requests by command hardis:work:save
Automated sources cleaning
You can configure automated cleaning of sources before creating merge requests, using command hardis:work:save
Those cleanings can be:
- Deletion of sources existing in
destructiveChanges.xml
- Remove from Profiles elements that are existing in Permission Sets, like Objects access configuration.
-
etc ...
All configuration properties
.sfdx-hardis.yml allows to make your project highly configuration. Have a look at its list of configuration properties !