sfdcsig/salesforce repository overview

⁠Code Coverage

Your changes get validated in a empty test org every time you check changes in. This must pass before changes can be merged into UAT. This includes tests passing. A new file has been added to the root of the repository. This is a json file that maps the apex classes and triggers to the test that has the coverage. It is the responsability of the developer to add the mapping to the file if it doesn't already exist. The json file is named test-coverage.json. When adding anything to the file please keep everything in alphabetical order, and keep the formating the same.

⁠Upcoming Releases

https://sig-synopsys.my.salesforce.com/a3g?fcf=00B340000096MV6⁠

⁠Pipeline Configuration

Pipelines is using oAuth2 jwt as login verification. Documentation can be found here on how to set it up. https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm⁠

The server.key is encrytped and stored as a bitbucket pipeline variable.

---

⁠Clone a repository

Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, download and install first⁠. If you prefer to clone from the command line, see Clone a repository⁠.

1. You’ll see the clone button under the Source heading. Click that button.
2. Now click Check out in SourceTree. You may need to create a SourceTree account or log in.
3. When you see the Clone New dialog in SourceTree, update the destination path and name if you’d like to and then click Clone.
4. Open the directory you just created to see your repository’s files.

Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can push your change back to Bitbucket with SourceTree⁠, or you can add, commit,⁠ and push from the command line⁠.