diff --git a/.gitbook/assets/image (1).png b/.gitbook/assets/image (1).png index 0d6aaef..05c6b05 100644 Binary files a/.gitbook/assets/image (1).png and b/.gitbook/assets/image (1).png differ diff --git a/.gitbook/assets/image (10).png b/.gitbook/assets/image (10).png index 7656c8c..975bbfd 100644 Binary files a/.gitbook/assets/image (10).png and b/.gitbook/assets/image (10).png differ diff --git a/.gitbook/assets/image (11).png b/.gitbook/assets/image (11).png index e06e2c8..3513112 100644 Binary files a/.gitbook/assets/image (11).png and b/.gitbook/assets/image (11).png differ diff --git a/.gitbook/assets/image (12).png b/.gitbook/assets/image (12).png index 38fcb40..b3b41b7 100644 Binary files a/.gitbook/assets/image (12).png and b/.gitbook/assets/image (12).png differ diff --git a/.gitbook/assets/image (13).png b/.gitbook/assets/image (13).png index d97c24f..0d6aaef 100644 Binary files a/.gitbook/assets/image (13).png and b/.gitbook/assets/image (13).png differ diff --git a/.gitbook/assets/image (14).png b/.gitbook/assets/image (14).png index 870f889..e06e2c8 100644 Binary files a/.gitbook/assets/image (14).png and b/.gitbook/assets/image (14).png differ diff --git a/.gitbook/assets/image (15).png b/.gitbook/assets/image (15).png index 7dea73b..47eed52 100644 Binary files a/.gitbook/assets/image (15).png and b/.gitbook/assets/image (15).png differ diff --git a/.gitbook/assets/image (16).png b/.gitbook/assets/image (16).png index 688b48e..7656c8c 100644 Binary files a/.gitbook/assets/image (16).png and b/.gitbook/assets/image (16).png differ diff --git a/.gitbook/assets/image (17).png b/.gitbook/assets/image (17).png index a3d763d..c19add6 100644 Binary files a/.gitbook/assets/image (17).png and b/.gitbook/assets/image (17).png differ diff --git a/.gitbook/assets/image (18).png b/.gitbook/assets/image (18).png index 68f6953..cc46cbf 100644 Binary files a/.gitbook/assets/image (18).png and b/.gitbook/assets/image (18).png differ diff --git a/.gitbook/assets/image (19).png b/.gitbook/assets/image (19).png index 4bb8d12..f41fe2d 100644 Binary files a/.gitbook/assets/image (19).png and b/.gitbook/assets/image (19).png differ diff --git a/.gitbook/assets/image (2).png b/.gitbook/assets/image (2).png index 7c9c20e..38fcb40 100644 Binary files a/.gitbook/assets/image (2).png and b/.gitbook/assets/image (2).png differ diff --git a/.gitbook/assets/image (20).png b/.gitbook/assets/image (20).png index 7b2358c..deb3d5d 100644 Binary files a/.gitbook/assets/image (20).png and b/.gitbook/assets/image (20).png differ diff --git a/.gitbook/assets/image (21).png b/.gitbook/assets/image (21).png index dc6714c..4b54a0d 100644 Binary files a/.gitbook/assets/image (21).png and b/.gitbook/assets/image (21).png differ diff --git a/.gitbook/assets/image (22).png b/.gitbook/assets/image (22).png index 6d51b86..6c6c10c 100644 Binary files a/.gitbook/assets/image (22).png and b/.gitbook/assets/image (22).png differ diff --git a/.gitbook/assets/image (23).png b/.gitbook/assets/image (23).png index b97ce23..b3b41b7 100644 Binary files a/.gitbook/assets/image (23).png and b/.gitbook/assets/image (23).png differ diff --git a/.gitbook/assets/image (24).png b/.gitbook/assets/image (24).png index f86d489..4df2b5a 100644 Binary files a/.gitbook/assets/image (24).png and b/.gitbook/assets/image (24).png differ diff --git a/.gitbook/assets/image (25).png b/.gitbook/assets/image (25).png index 47eed52..9469436 100644 Binary files a/.gitbook/assets/image (25).png and b/.gitbook/assets/image (25).png differ diff --git a/.gitbook/assets/image (26).png b/.gitbook/assets/image (26).png index 4df2b5a..d97c24f 100644 Binary files a/.gitbook/assets/image (26).png and b/.gitbook/assets/image (26).png differ diff --git a/.gitbook/assets/image (27) (1).png b/.gitbook/assets/image (27) (1).png new file mode 100644 index 0000000..414846f Binary files /dev/null and b/.gitbook/assets/image (27) (1).png differ diff --git a/.gitbook/assets/image (27).png b/.gitbook/assets/image (27).png index 414846f..b97ce23 100644 Binary files a/.gitbook/assets/image (27).png and b/.gitbook/assets/image (27).png differ diff --git a/.gitbook/assets/image (29) (1).png b/.gitbook/assets/image (29) (1).png new file mode 100644 index 0000000..a14ed58 Binary files /dev/null and b/.gitbook/assets/image (29) (1).png differ diff --git a/.gitbook/assets/image (29).png b/.gitbook/assets/image (29).png index a14ed58..68f6953 100644 Binary files a/.gitbook/assets/image (29).png and b/.gitbook/assets/image (29).png differ diff --git a/.gitbook/assets/image (3).png b/.gitbook/assets/image (3).png index d6b4260..dc6714c 100644 Binary files a/.gitbook/assets/image (3).png and b/.gitbook/assets/image (3).png differ diff --git a/.gitbook/assets/image (30) (1).png b/.gitbook/assets/image (30) (1).png new file mode 100644 index 0000000..9a3b62c Binary files /dev/null and b/.gitbook/assets/image (30) (1).png differ diff --git a/.gitbook/assets/image (30).png b/.gitbook/assets/image (30).png index 9a3b62c..70d4649 100644 Binary files a/.gitbook/assets/image (30).png and b/.gitbook/assets/image (30).png differ diff --git a/.gitbook/assets/image (32).png b/.gitbook/assets/image (32).png index 70d4649..2c3bd60 100644 Binary files a/.gitbook/assets/image (32).png and b/.gitbook/assets/image (32).png differ diff --git a/.gitbook/assets/image (36) (1).png b/.gitbook/assets/image (36) (1).png new file mode 100644 index 0000000..343f568 Binary files /dev/null and b/.gitbook/assets/image (36) (1).png differ diff --git a/.gitbook/assets/image (36).png b/.gitbook/assets/image (36).png index 343f568..304e6ff 100644 Binary files a/.gitbook/assets/image (36).png and b/.gitbook/assets/image (36).png differ diff --git a/.gitbook/assets/image (4).png b/.gitbook/assets/image (4).png index 4d9b681..d27fe38 100644 Binary files a/.gitbook/assets/image (4).png and b/.gitbook/assets/image (4).png differ diff --git a/.gitbook/assets/image (41).png b/.gitbook/assets/image (41).png index 12d0aa2..4bb8d12 100644 Binary files a/.gitbook/assets/image (41).png and b/.gitbook/assets/image (41).png differ diff --git a/.gitbook/assets/image (42).png b/.gitbook/assets/image (42).png index 6c6c10c..ea4d7d1 100644 Binary files a/.gitbook/assets/image (42).png and b/.gitbook/assets/image (42).png differ diff --git a/.gitbook/assets/image (43).png b/.gitbook/assets/image (43).png index deb3d5d..870f889 100644 Binary files a/.gitbook/assets/image (43).png and b/.gitbook/assets/image (43).png differ diff --git a/.gitbook/assets/image (44).png b/.gitbook/assets/image (44).png index 4b54a0d..6795382 100644 Binary files a/.gitbook/assets/image (44).png and b/.gitbook/assets/image (44).png differ diff --git a/.gitbook/assets/image (45).png b/.gitbook/assets/image (45).png index 304e6ff..a3d763d 100644 Binary files a/.gitbook/assets/image (45).png and b/.gitbook/assets/image (45).png differ diff --git a/.gitbook/assets/image (46).png b/.gitbook/assets/image (46).png index bb343a6..8a52c5b 100644 Binary files a/.gitbook/assets/image (46).png and b/.gitbook/assets/image (46).png differ diff --git a/.gitbook/assets/image (47).png b/.gitbook/assets/image (47).png index ea4d7d1..12d0aa2 100644 Binary files a/.gitbook/assets/image (47).png and b/.gitbook/assets/image (47).png differ diff --git a/.gitbook/assets/image (48).png b/.gitbook/assets/image (48).png index 2c3bd60..d6b4260 100644 Binary files a/.gitbook/assets/image (48).png and b/.gitbook/assets/image (48).png differ diff --git a/.gitbook/assets/image (5).png b/.gitbook/assets/image (5).png index 6795382..7c9c20e 100644 Binary files a/.gitbook/assets/image (5).png and b/.gitbook/assets/image (5).png differ diff --git a/.gitbook/assets/image (50).png b/.gitbook/assets/image (50).png index 3513112..bb343a6 100644 Binary files a/.gitbook/assets/image (50).png and b/.gitbook/assets/image (50).png differ diff --git a/.gitbook/assets/image (51).png b/.gitbook/assets/image (51).png index 9469436..6d51b86 100644 Binary files a/.gitbook/assets/image (51).png and b/.gitbook/assets/image (51).png differ diff --git a/.gitbook/assets/image (52).png b/.gitbook/assets/image (52).png index b3b41b7..688b48e 100644 Binary files a/.gitbook/assets/image (52).png and b/.gitbook/assets/image (52).png differ diff --git a/.gitbook/assets/image (6).png b/.gitbook/assets/image (6).png index d27fe38..7dea73b 100644 Binary files a/.gitbook/assets/image (6).png and b/.gitbook/assets/image (6).png differ diff --git a/.gitbook/assets/image (7).png b/.gitbook/assets/image (7).png index 05c6b05..f86d489 100644 Binary files a/.gitbook/assets/image (7).png and b/.gitbook/assets/image (7).png differ diff --git a/.gitbook/assets/image (8).png b/.gitbook/assets/image (8).png index eff1eb9..4d9b681 100644 Binary files a/.gitbook/assets/image (8).png and b/.gitbook/assets/image (8).png differ diff --git a/.gitbook/assets/image (9).png b/.gitbook/assets/image (9).png index 975bbfd..eff1eb9 100644 Binary files a/.gitbook/assets/image (9).png and b/.gitbook/assets/image (9).png differ diff --git a/.gitbook/assets/image.png b/.gitbook/assets/image.png index 8a52c5b..7b2358c 100644 Binary files a/.gitbook/assets/image.png and b/.gitbook/assets/image.png differ diff --git a/.gitbook/assets/sivanand.jothy (1).jpg b/.gitbook/assets/sivanand.jothy (1).jpg index d814564..698602d 100644 Binary files a/.gitbook/assets/sivanand.jothy (1).jpg and b/.gitbook/assets/sivanand.jothy (1).jpg differ diff --git a/.gitbook/assets/sivanand.jothy.jpg b/.gitbook/assets/sivanand.jothy.jpg index 698602d..d814564 100644 Binary files a/.gitbook/assets/sivanand.jothy.jpg and b/.gitbook/assets/sivanand.jothy.jpg differ diff --git a/about-us/contributors.md b/about-us/contributors.md index 5c48757..150482c 100644 --- a/about-us/contributors.md +++ b/about-us/contributors.md @@ -31,11 +31,11 @@ Jothy Sivanand - is Accenture Certified Senior Technology Architect and an inven Ramesh is a Senior DevOps Engineer with good knowledge of key DevOps practices – Continuous Integration and Delivery, Strategy, Implementation, Security and Vulnerability Management (CDP) and Cloud concepts (AWS/Azure) - IaaS, PaaS, SaaS. He has been involved and part of DX@Scale journey since 2019 as an engineer, advocate, contributor, implementer, maintainer, trouble-shooter and successfully implemented CICD solutions for Salesforce on large/small scale projects. -![Hung Dinh](<../.gitbook/assets/image (24).png>) +![Hung Dinh](<../.gitbook/assets/image (7).png>) Hung set out the mission to tackle Salesforce DevOps practices head-on after he had been involved in delivering a large Salesforce transformation program and appalled at how far behind the DevOps capabilities were. Hung acts as an advisor to DX@Scale core team on tooling and practices.​ -![Eric Shen](<../.gitbook/assets/image (26).png>) +![Eric Shen](<../.gitbook/assets/image (24).png>) Eric is a Salesforce Technical Architect who has been using sfpower\* tools across multiple programs. He contributes additions and fixes to documentation, as well provide feedback on the various commands. @@ -45,6 +45,6 @@ Diefffrei is a salesforce architect at Expereo, He has been working on salesforc -![Kevin Jones](<../.gitbook/assets/image (51).png>) +![Kevin Jones](<../.gitbook/assets/image (25).png>) Kevin is a principal architect at FinancialForce where he focuses on product performance & scalability alongside developer tooling. He develops a set of open-source libraries and VSCode extensions for analysing Salesforce metadata and debug logs. Working for a large ISV has given him plenty of first hand experience of the difficulties of managing, analysing and refactoring metadata. He sees great value in the way DX@Scale is optimising the developer experience for everyone working on the platform. diff --git a/challenges/challenges/2.-using-source-format.md b/challenges/challenges/2.-using-source-format.md index 8dfc4f1..bc64324 100644 --- a/challenges/challenges/2.-using-source-format.md +++ b/challenges/challenges/2.-using-source-format.md @@ -209,7 +209,7 @@ Once the metadata is successfully committed, commit your changes to the repo. * Get the newly created repo URL -![](<../../.gitbook/assets/image (12).png>) +![](<../../.gitbook/assets/image (2).png>) * Follow the below commands in the order from your Terminal to publish your local repo diff --git a/challenges/challenges/5.-scratch-org-shape.md b/challenges/challenges/5.-scratch-org-shape.md index e0bb7d9..07bd59d 100644 --- a/challenges/challenges/5.-scratch-org-shape.md +++ b/challenges/challenges/5.-scratch-org-shape.md @@ -83,7 +83,7 @@ Try [`sfdx sfpowerkit:package:dependencies:install`](https://github.com/accentur * Go to Setup > Sharing Settings > Account Sharing Rules > New -![The details to be used on the sharing rule](<../../.gitbook/assets/image (4).png>) +![The details to be used on the sharing rule](<../../.gitbook/assets/image (8).png>) * Check the status using the [sfdx force:source:status](https://developer.salesforce.com/docs/atlas.en-us.sfdx\_cli\_reference.meta/sfdx\_cli\_reference/cli\_reference\_force\_source.htm#cli\_reference\_status) command * Pull the changes using [sfdx force:source:pull](https://developer.salesforce.com/docs/atlas.en-us.sfdx\_cli\_reference.meta/sfdx\_cli\_reference/cli\_reference\_force\_source.htm#cli\_reference\_pull) command diff --git a/challenges/challenges/7.-create-your-own-package.md b/challenges/challenges/7.-create-your-own-package.md index 8488a63..aa293d6 100644 --- a/challenges/challenges/7.-create-your-own-package.md +++ b/challenges/challenges/7.-create-your-own-package.md @@ -18,7 +18,7 @@ * Search for and click 'DevHub' in the Quick Find menu * Select 'Enable Unlocked Packages and Second-Generation Managed Packages' -![](<../../.gitbook/assets/image (5).png>) +![](<../../.gitbook/assets/image (44).png>) ### Create an Unlocked package diff --git a/challenges/challenges/scratch-org-pooling-part-2-prepare.md b/challenges/challenges/scratch-org-pooling-part-2-prepare.md index 981a9f6..5f3b0ae 100644 --- a/challenges/challenges/scratch-org-pooling-part-2-prepare.md +++ b/challenges/challenges/scratch-org-pooling-part-2-prepare.md @@ -26,7 +26,7 @@ Good news! If you completed [Scratch Org Pooling Part 1](scratch-org-pooling.md) * Click on 'Actions' in your Dreamhouse-App repo -![](<../../.gitbook/assets/image (15).png>) +![](<../../.gitbook/assets/image (6).png>) * Create a new workflow and name it 'prepare' * Replace the contents of the file with the file below @@ -127,11 +127,11 @@ Select 'New repository secret' * Go back to actions and select the workflow -![](<../../.gitbook/assets/image (16).png>) +![](<../../.gitbook/assets/image (52).png>) * Run the workflow by selecting 'run workflow' -![](<../../.gitbook/assets/image (17).png>) +![](<../../.gitbook/assets/image (45).png>) * Select the job to watch it running through the tasks and create the scratch orgs required diff --git a/challenges/challenges/validating-your-changes.md b/challenges/challenges/validating-your-changes.md index 60ba7f3..fca169f 100644 --- a/challenges/challenges/validating-your-changes.md +++ b/challenges/challenges/validating-your-changes.md @@ -33,7 +33,7 @@ sfdx sfpowerscripts:orchestrator:validate --help * Click on 'Actions' in your Dreamhouse-App repo -![](<../../.gitbook/assets/image (15).png>) +![](<../../.gitbook/assets/image (6).png>) * Create a new workflow and name it 'validate' * Replace the contents of the file with the file below diff --git a/challenges/prerequisites.md b/challenges/prerequisites.md index be34d75..ab391f2 100644 --- a/challenges/prerequisites.md +++ b/challenges/prerequisites.md @@ -75,7 +75,7 @@ sfdx plugins:install @dxatscale/sfpowerscripts 2. Go to [https://trailhead.salesforce.com/users/profiles/orgs](https://trailhead.salesforce.com/users/profiles/orgs%20) 3. Create 2 trailhead playgrounds -![](<../.gitbook/assets/image (8) (1) (1) (1) (1).png>) +![](<../.gitbook/assets/image (8) (1) (1) (1) (1) (1).png>) ## Signup for your own Github Account diff --git a/ci-cd/artifacts.md b/ci-cd/artifacts.md index 51c91aa..13b5139 100644 --- a/ci-cd/artifacts.md +++ b/ci-cd/artifacts.md @@ -16,7 +16,7 @@ Why do you need an artifact registry? Let's have a look at the below example, here a CI pipeline creates a bunch of artifacts/packages, then the publish command is used to publish these artifacts into an Artifact Registry. This stage often gets repeated multiple times during a day. -![](<../.gitbook/assets/image (44).png>) +![](<../.gitbook/assets/image (21).png>) An important thing to note here is especially when a CI pipeline is enabled with 'diffcheck' functionality, it only builds packages for the particular build run. Unless you are immediately deploying these packages to production, there is no way to deploy an entire set of packages other than going through each of the build runs and immediately pushing them into production. You will need to aggregate packages before you proceed to the next stage. diff --git a/environment/pooling-scratch-orgs.md b/environment/pooling-scratch-orgs.md index 9a3424c..0163738 100644 --- a/environment/pooling-scratch-orgs.md +++ b/environment/pooling-scratch-orgs.md @@ -42,7 +42,7 @@ It is highly recommended to build a delete pool pipeline that could be triggered Scratch Org Pools can be monitored using an analytic tool like DataDog or New Relic. Check sfpowerscripts documentation to understand the [metrics](../sfpowerscripts/metrics-and-dashboards.md) emitted by sfpowerscripts. A sample dashboard is attached below -![](<../.gitbook/assets/image (23).png>) +![](<../.gitbook/assets/image (27).png>) To learn more about how to build a pool of scratch orgs using sfpowerscripts, click on the link below diff --git a/environment/refreshing-sandboxes.md b/environment/refreshing-sandboxes.md index 434568c..47688ba 100644 --- a/environment/refreshing-sandboxes.md +++ b/environment/refreshing-sandboxes.md @@ -6,7 +6,7 @@ When refreshing sandboxes from production, care must be taken to address the fol A sandbox could be refreshed at any point in time, provided your runbook is accurate and well defined {% endhint %} -![Sandbox Refresh Interval](<../.gitbook/assets/image (22).png>) +![Sandbox Refresh Interval](<../.gitbook/assets/image (51).png>) Read more about refreshing Partial or Fully Copy Sandboxes [here](https://help.salesforce.com/articleView?id=000313358\&type=1\&mode=1). diff --git a/implementing-your-ci-cd/azure-devops/getting-started.md b/implementing-your-ci-cd/azure-devops/getting-started.md index 2bf29d2..88e34eb 100644 --- a/implementing-your-ci-cd/azure-devops/getting-started.md +++ b/implementing-your-ci-cd/azure-devops/getting-started.md @@ -63,7 +63,7 @@ To enable modular package development, there are a few configurations in Salesfo 2. Go to **Development > Dev Hub** 3. Toggle the button to on for **Enable Dev Hub** -![](<../../.gitbook/assets/image (10).png>) +![](<../../.gitbook/assets/image (16).png>) ### B. Enable Unlocked Packages and Second-Generation Managed Packages @@ -90,7 +90,7 @@ For auditing purposes, it is best practice to create a separate [service account 7. Set **Profile** to **System Administrator** 8. Scroll down and click on **Save** -![](<../../.gitbook/assets/image (18).png>) +![](<../../.gitbook/assets/image (29).png>) {% hint style="info" %} Only certain [editions](https://help.salesforce.com/s/articleView?id=000326486\&type=1) of Salesforce has API Access. It's best to create a new **Profile** or **Permission Set** and configure the **System Permissions** and enable the **API Enabled** and **Api Only User** permission. diff --git a/implementing-your-ci-cd/github/getting-started.md b/implementing-your-ci-cd/github/getting-started.md index 510dc5a..5ee3c6c 100644 --- a/implementing-your-ci-cd/github/getting-started.md +++ b/implementing-your-ci-cd/github/getting-started.md @@ -59,7 +59,7 @@ To enable modular package development, there are a few configurations in Salesfo 2. Go to **Development > Dev Hub** 3. Toggle the button to on for **Enable Dev Hub** -![](<../../.gitbook/assets/image (10).png>) +![](<../../.gitbook/assets/image (16).png>) ### B. Enable Unlocked Packages and Second-Generation Managed Packages @@ -84,7 +84,7 @@ For auditing purposes, it is best practice to create a separate [service account 7. Set **Profile** to **System Administrator** 8. Scroll down and click on **Save** -![](<../../.gitbook/assets/image (18).png>) +![](<../../.gitbook/assets/image (29).png>) {% hint style="info" %} Only certain [editions](https://help.salesforce.com/s/articleView?id=000326486\&type=1) of Salesforce has API Access. It's best to create a new **Profile** or **Permission Set** and configure the **System Permissions** and enable the **API Enabled** and **Api Only User** permission. diff --git a/implementing-your-ci-cd/gitlab/getting-started.md b/implementing-your-ci-cd/gitlab/getting-started.md index d7a8e1d..d309108 100644 --- a/implementing-your-ci-cd/gitlab/getting-started.md +++ b/implementing-your-ci-cd/gitlab/getting-started.md @@ -59,7 +59,7 @@ To enable modular package development, there are a few configurations in Salesfo 2. Go to **Development > Dev Hub** 3. Toggle the button to on for **Enable Dev Hub** -![](<../../.gitbook/assets/image (10).png>) +![](<../../.gitbook/assets/image (16).png>) ### B. Enable Unlocked Packages and Second-Generation Managed Packages @@ -84,7 +84,7 @@ For auditing purposes, it is best practice to create a separate [service account 7. Set **Profile** to **System Administrator** 8. Scroll down and click on **Save** -![](<../../.gitbook/assets/image (18).png>) +![](<../../.gitbook/assets/image (29).png>) {% hint style="info" %} Only certain [editions](https://help.salesforce.com/s/articleView?id=000326486\&type=1) of Salesforce has API Access. It's best to create a new **Profile** or **Permission Set** and configure the **System Permissions** and enable the **API Enabled** and **Api Only User** permission. @@ -260,9 +260,9 @@ Project Access Tokens are only supported on self-managed instances on Free tier 7. Leave **Environment Scope** to **All (default)** 8. Click on **Add variable** to save -![](<../../.gitbook/assets/image (8).png>) +![](<../../.gitbook/assets/image (9).png>) -![](<../../.gitbook/assets/image (25).png>) +![](<../../.gitbook/assets/image (15).png>) Repeat the steps above and create the following variables below using the sfdxAuthUrl created earlier from the Salesforce CLI. @@ -283,7 +283,7 @@ Repeat the steps above and create the following variables below using the sfdxAu | UAT\_ALIAS | uat | Variable | All (default) | No | No | | UAT\_SFDX\_AUTH\_URL | \ | File | All (default) | No | Yes | -![Project Variables](<../../.gitbook/assets/image (3).png>) +![Project Variables](<../../.gitbook/assets/image (48).png>) {% hint style="info" %} The NPM\_SCOPE variable should start with the @ character. Read more about npm scope [here](https://docs.npmjs.com/cli/v7/using-npm/scope). @@ -299,7 +299,7 @@ The [dxatscale-template](https://github.com/dxatscale/dxatscale-template) reposi git clone https://github.com/dxatscale/dxatscale-template.git ``` -![](<../../.gitbook/assets/image (3).png>) +![](<../../.gitbook/assets/image (48).png>) ### B. Clone Project Repository @@ -311,7 +311,7 @@ git clone https://github.com/dxatscale/dxatscale-template.git git clone git@gitlab.com:groupname/dxatscale-poc.git ``` -![](<../../.gitbook/assets/image (6).png>) +![](<../../.gitbook/assets/image (4).png>) ### C. Copy Template Contents to Project Folder @@ -362,7 +362,7 @@ Once the files have been committed, you can verify the files have been pushed th 1. Navigate to **Repository > Files** 2. Verify all the files are visible in the repository -![](<../../.gitbook/assets/image (29).png>) +![](<../../.gitbook/assets/image (29) (1).png>) 1. Navigate to **CI/CD > Pipelines** 2. Verify the pipeline has been skipped @@ -540,7 +540,7 @@ Prior to creating the scratch org pools, an initial version of artifacts should 2. Navigate to **Package & Registries > Package Registry** 3. Verify that the latest **core** artifact has been created and tagged with **main** label. -![](<../../.gitbook/assets/image (27).png>) +![](<../../.gitbook/assets/image (27) (1).png>) ### G. Scheduled Jobs diff --git a/implementing-your-ci-cd/gitlab/solution-overview.md b/implementing-your-ci-cd/gitlab/solution-overview.md index 20c50c7..3e021e9 100644 --- a/implementing-your-ci-cd/gitlab/solution-overview.md +++ b/implementing-your-ci-cd/gitlab/solution-overview.md @@ -72,7 +72,7 @@ The [.gitlab-ci.yml](https://docs.gitlab.com/ee/ci/yaml/gitlab\_ci\_yaml.html) t In the template file provided, the structure of the [YAML](https://yaml.org) file follows the following structure: -![Template Code Structure](<../../.gitbook/assets/image (36).png>) +![Template Code Structure](<../../.gitbook/assets/image (36) (1).png>) | Section | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | @@ -95,7 +95,7 @@ In the template file provided, the structure of the [YAML](https://yaml.org) fil The diagram below depicts the various stages and jobs configured in the GitLab CI/CD configuration file .gitlab-ci.yml which incorporates the [sfpowerscripts orchestrator](https://sfpowerscripts.dxatscale.io/faq/orchestrator) and [sfpowerkit package](https://www.npmjs.com/package/sfpowerkit#sfpowerkitpackagevalid) commands to manage your CI/CD process. The grouping of stages and jobs are split into merge requests, merges, and manual triggers of the pipeline. -![](<../../.gitbook/assets/image (14).png>) +![](<../../.gitbook/assets/image (43).png>) | Type | Stage | Job | Command | Description | | ------------- | ---------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | @@ -111,7 +111,7 @@ The diagram below depicts the various stages and jobs configured in the GitLab C The diagram below highlights the [dxatscale-template](https://github.com/dxatscale/dxatscale-template) recommended scheduled jobs and manual job for Scratch Org Pool Management. The stages and jobs configured in the GitLab CI/CD configuration file .gitlab-ci.yml uses the sfpowerscripts prepare commands to build scratch org pools for Developer and CI Scratch Orgs. Additional schedule job for publishing metrics to your dashboard platform is provided as well. -![](<../../.gitbook/assets/image (30).png>) +![](<../../.gitbook/assets/image (30) (1).png>) | Type | Stage | Job | Command | Description | | --------- | ------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | diff --git a/media-library/knowledge-articles/building-packages-for-deployment.md b/media-library/knowledge-articles/building-packages-for-deployment.md index 39d940b..f6e584a 100644 --- a/media-library/knowledge-articles/building-packages-for-deployment.md +++ b/media-library/knowledge-articles/building-packages-for-deployment.md @@ -12,7 +12,7 @@ sfpowerscripts provides two specific commands that can help use here. These comm Let’s first discuss **quickbuild**! This command creates your package version and bundles it into an artifact. It does so without validating any dependencies or test coverage. -![](<../../.gitbook/assets/image (21).png>) +![](<../../.gitbook/assets/image (3).png>) This command is recommended when wanting to deploy to a ‘developer’ or ST sandbox to validate code before attempting a full build. It has no required flags but must be triggered from within the project directory (if you are using unlocked packages, dev hub becomes mandatory) diff --git a/media-library/knowledge-articles/effective-pull-reviews-in-salesforce-dx-development-persistent-ci.md b/media-library/knowledge-articles/effective-pull-reviews-in-salesforce-dx-development-persistent-ci.md index a5f744e..fff7e47 100644 --- a/media-library/knowledge-articles/effective-pull-reviews-in-salesforce-dx-development-persistent-ci.md +++ b/media-library/knowledge-articles/effective-pull-reviews-in-salesforce-dx-development-persistent-ci.md @@ -4,7 +4,7 @@ description: Published on November 26, 2018 by Azlam Abdulsalam # Effective Pull Reviews in Salesforce DX Development - Persistent CI -![](<../../.gitbook/assets/image (2).png>) +![](<../../.gitbook/assets/image (5).png>) Salesforce DX is a combination of technologies and practices that bring modern development practices such as open and standard developer experience driven by a CLI (Command Line Interface), Repeatable deployment using packaging, automated testing and predominantly source driven development diff --git a/media-library/knowledge-articles/is-it-time-to-roll-your-own-ci-cd-for-salesforce.md b/media-library/knowledge-articles/is-it-time-to-roll-your-own-ci-cd-for-salesforce.md index 6f9f403..149ff19 100644 --- a/media-library/knowledge-articles/is-it-time-to-roll-your-own-ci-cd-for-salesforce.md +++ b/media-library/knowledge-articles/is-it-time-to-roll-your-own-ci-cd-for-salesforce.md @@ -4,7 +4,7 @@ description: Published on November 6, 2019 by Azlam Abdulsalam # Is it time to roll your own CI/CD for Salesforce? -![](../../.gitbook/assets/image.png) +![](<../../.gitbook/assets/image (46).png>) CI/CD for Salesforce is in a very exciting phase. On one end you have awesome 'only for Salesforce' DevOps platforms such as Autorabit, Gearset, Copado etc which gets you going as quickly as possible. On the other end, often in the case of large enterprises, a custom-built pipeline is often the preferred choice. diff --git a/sfpowerscripts/metrics-and-dashboards.md b/sfpowerscripts/metrics-and-dashboards.md index b5908df..b1f98f7 100644 --- a/sfpowerscripts/metrics-and-dashboards.md +++ b/sfpowerscripts/metrics-and-dashboards.md @@ -122,4 +122,4 @@ The following are the list of metrics that are captured. ![](../.gitbook/assets/dashboard\_edited.png) -![](<../.gitbook/assets/image (52) (1) (1) (1).png>) +![](<../.gitbook/assets/image (52) (1) (1).png>) diff --git a/sfpowerscripts/orchestrator/build-and-quick-build.md b/sfpowerscripts/orchestrator/build-and-quick-build.md index 96902b2..53acebf 100644 --- a/sfpowerscripts/orchestrator/build-and-quick-build.md +++ b/sfpowerscripts/orchestrator/build-and-quick-build.md @@ -29,7 +29,7 @@ These commands follow the order of the the packages as ordered in your sfdx-proj **Scenario 1 : Build All** -![](<../../.gitbook/assets/image (43).png>) +![](<../../.gitbook/assets/image (20).png>) 1. Trigger creation of package A 2. Once A is completed, trigger creation of package B & C \*\*,\*\*using the version of A, created in step 1 @@ -37,13 +37,13 @@ These commands follow the order of the the packages as ordered in your sfdx-proj **Scenario 2 : Build with diffCheck enabled on a package with no dependencies** -![](<../../.gitbook/assets/image (53).png>) +![](<../../.gitbook/assets/image (18).png>) In this scenario, where only a single package has changed and **diffCheck** is enabled, the build command will only trigger the creation of Package B **Scenario 3 : Build with diffCheck enabled on changes in multiple packages** -![](<../../.gitbook/assets/image (50).png>) +![](<../../.gitbook/assets/image (11).png>) In this scenario, where there are changes in multiple packages, say B & C, the build command will trigger these packages in parallel, as their dependent package A has not changed (hence fulfilled). Please note even though there is a change in C, package D will not be triggered, unless there is an explicit version change of version number (major.minor.patch) of package D diff --git a/sfpowerscripts/orchestrator/deploy.md b/sfpowerscripts/orchestrator/deploy.md index a6cf930..3fc8ac2 100644 --- a/sfpowerscripts/orchestrator/deploy.md +++ b/sfpowerscripts/orchestrator/deploy.md @@ -51,7 +51,7 @@ There are some certain situations, due to integrity concerns (especially around The `--baselineorg` parameter allows you to specify the alias or username of an org against which to check whether the incoming package versions have already been installed and form a deployment plan.This overrides the default behaviour which is to compare against the deployment target org. This is an optional feature which allows to ensure each org's are updated with the same deployment across every org's in the path to production. -![](<../../.gitbook/assets/image (32).png>) +![](<../../.gitbook/assets/image (30).png>) ### Using deploy in a non-linear pipeline diff --git a/sfpowerscripts/orchestrator/prepare/README.md b/sfpowerscripts/orchestrator/prepare/README.md index b6bf9a5..bde14cb 100644 --- a/sfpowerscripts/orchestrator/prepare/README.md +++ b/sfpowerscripts/orchestrator/prepare/README.md @@ -172,7 +172,7 @@ Package checkpoints allow precise control over which scratch orgs are committed When you are using prepare in larger repositories with multiple managed packages, the process of preparing a scratch org can be extremely slow, often running above 6 hours. If you are preparing using cloud hosted agents of a CI/CD platform, most of the platforms are designed to timeout within a certain time window. This could result in unavailability of scratch orgs in pools, as most scratch orgs will be in 'IN PROGRESS' state and can only reclaimed by deleting the pool as there are no agents to continue the remaining progress or change the stage of the orgs. This is where you could use prepare in multiple stages. -![Daisy chaining scratch org pools ](<../../../.gitbook/assets/image (54).png>) +![Daisy chaining scratch org pools ](<../../../.gitbook/assets/image (17).png>) In the above image, CI2 Pool is using CI Snapshot pool prepared in an earlier stage or job. The CI2 Pool definition will be utilizing 'snapshotPool' as a property which points to 'CI Snapshot' pool. Any packages that are installed on CI Snapshot pool are skipped while preparing CI2 Pools. diff --git a/sfpowerscripts/sfpowerscripts.md b/sfpowerscripts/sfpowerscripts.md index 27c41e4..ed4a146 100644 --- a/sfpowerscripts/sfpowerscripts.md +++ b/sfpowerscripts/sfpowerscripts.md @@ -41,7 +41,7 @@ The following package creation commands shows this in action * Create Unlocked Package (including Org dependent unlocked packages) * Create Data Package, for Records Based Configuration, such as Vlocity datapacks -![](<../.gitbook/assets/image (42).png>) +![](<../.gitbook/assets/image (22).png>) These commands create an artifact named`_sfpowerscripts_artifact_.zip`. This zip file contains the following items diff --git a/sfpowerscripts/types-of-packaging/data-packages.md b/sfpowerscripts/types-of-packaging/data-packages.md index 1b87c1f..29e0f93 100644 --- a/sfpowerscripts/types-of-packaging/data-packages.md +++ b/sfpowerscripts/types-of-packaging/data-packages.md @@ -30,7 +30,7 @@ Simply add an entry in the package directories, providing the package's name, pa Export your Salesforce records to csv files using the [SFDMU plugin](https://github.com/forcedotcom/SFDX-Data-Move-Utility). For more information on plugin installation, creating an export.json file, and exporting to csv files, refer to _Plugin Basic > Basic Usage_ in SFDMU's [documentation](https://help.sfdmu.com/quick-start). -![](<../../.gitbook/assets/image (47).png>) +![](<../../.gitbook/assets/image (42).png>) ## **Options with Data Packages** @@ -67,7 +67,7 @@ sfdx force:apex:execute -f scripts/datascript.apex -u $2 sfpowerscripts support vlocity RBC migration usng the vlocity build tool (vbt). sfpowerscripts will be automatically able to detect whether a data package need to be deployed using vlocity or using sfdmu. (Please not to enable vlocity in preparing scratchOrgs, the enableVlocity flag need to be turned on in the pool configuration file) -![Defining a vlocity data package](<../../.gitbook/assets/image (46).png>) +![Defining a vlocity data package](<../../.gitbook/assets/image (50).png>) A vlocity data package need to have vlocityComponents.yaml file in the root of the package directory and it should have the following defintion