Skip to content

Conversation

@shetzel
Copy link
Contributor

@shetzel shetzel commented Aug 21, 2024

What does this PR do?

Requires and consumes SDR PR 1403; the zipSize and zipFileCount fields on SDR's DeployResult and the deployZipData event. Displays this zip data in deploy command output and JSON response.

What issues does this PR fix or reference?

@W-16488140@

To test:
link SDR PR 1403 branch to this branch
Run deploy commands of various kinds with and without --json. Note the zip size and zip file count output and fields.
Turn on debug output and look for debug lines about zip size and file count
check out telemetry event with this data added
the JSON response with deploy commands will always have the zipSize and zipFileCount fields added, as long as the data is there in the event.


before(async () => {
testkit = await TestSession.create({
project: { gitClone: 'https://github.com/salesforcecli/sample-project-multiple-packages' },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice (archived repo so it can't break the NUT) 😁

@cristiand391
Copy link
Member

QA notes:

✅ deploy with verbose, human/json output includes zip size/file count
✅ zip size/file count is included in metadata_api_deploy_result event:
Screenshot 2024-08-22 at 4 43 03 PM

NOTE: tested by enabling telemetry in debug mode:

SF_TELEMETRY_DEBUG=true SF_DISABLE_TELEMETRY=false sf project deploy start --source-dir force-app --verbose --dev-debug

then checking the payload written

✅ deploying a mdapi format folder shows both counters
✅ deploying a mdapi zip only shows zip size
✅ can see SDR msg in debug output

@cristiand391
Copy link
Member

re-ran tests in my comment above (before HRO changes), all 🟢

@cristiand391 cristiand391 merged commit a03a580 into main Aug 27, 2024
@cristiand391 cristiand391 deleted the sh/deploy-zip-size branch August 27, 2024 19:01
@iowillhoit iowillhoit changed the title Sh/deploy zip size W-16488140 Sh/deploy zip size Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants