Skip to content

Conversation

@sasandhu
Copy link

@sasandhu sasandhu commented Oct 21, 2025

Context

Describe the context or motivation for this PR. Include links to any related Azure DevOps Work Items or GitHub issues.
📌 How to link to ADO Work Items

CopyFiles@2 task fails to copy files if the source folder is very large with javascript heap out of memory issues. This is because the find function tries to loads the whole source folder into memory before matching with the file pattern glob.

Task Name

Name of the updated or newly created pipeline task.

CopyFiles@2

Description

Summarize the changes made in this PR clearly and concisely.

Use fast-glob instead of tl.find

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

Medium

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?


Tech Design / Approach

  • Design has been written and reviewed.
  • Any architectural decisions, trade-offs, and alternatives are captured.

None

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

  • User guides, API specs, system diagrams, or runbooks are updated.

None

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

No, since the functionality is the same

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

None

Logging Added/Updated (Yes/No)

  • Appropriate log statements are added with meaningful messages.
  • Logging does not expose sensitive data.
  • Log levels are used correctly (e.g., info, warn, error).

No

Telemetry Added/Updated (Yes/No)

  • Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
  • Events are tagged with proper metadata for filtering and analysis.
  • Telemetry is validated in staging or test environments.

No

Rollback Scenario and Process (Yes/No)

  • Rollback plan is documented.

No

Dependency Impact Assessed and Regression Tested (Yes/No)

  • All impacted internal modules, APIs, services, and third-party libraries are analyzed.
  • Results are reviewed and confirmed to not break existing functionality.

Checklist

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.

1 participant