Skip to content

This list is maintained in a best effort fashion and may not reflect all known issues.

Azure DevOps Extension v2.2 Limitations

These limits apply to the upcoming v2.2 release. See the migration guide before upgrading.

  • Credentials and host trust: retaining old connection inputs does not remove the need for SSH and Symitar credentials. Unknown or changed host keys fail without prompting; there is no automatic acceptance mode.
  • Source line endings: validation preserves saved bytes. Prepare PowerOn source/includes with LF endings; do not expect deployment to normalize them.
  • Concurrent writers: snapshots and checksums protect the selected mutation scope, but synchronization is not atomic and cannot prevent later external edits. Coordinate mirror runs on shared directories.
  • Rollback: recovery verifies source bytes and installation health. A failed rollback reports unknown destination state requiring investigation. Generated binaries and timestamps are not promised to be identical after rebuilding.
  • Dependent reinstalls: opt-in and limited to unpreserved parents in installPowerOns. Requires complete artifact source trees and exact casing. It does not discover server-only parents or infer dependencies from missing or divergent preserved files.
  • Dry-run scope: previews neither mutate files nor install programs, and do not prove future transfer, compilation, or rollback success. The real run recomputes its comparison against the current host.
  • Windows rsync: requires working WSL with Bash, setsid, rsync, and sshpass under the agent service account. A dry run does not prove rsync works. Check agent prerequisites before live transfers.
  • Transfer selection: SynchronizeDirectory still supports SFTP and rsync; checksum planning, snapshots, and verification use SFTP for both. ValidatePowerOn's accepted syncMethod input does not change its SFTP checksum comparison.
  • Pull-to-PR permissions: the Azure DevOps Build Service needs repository and branch permissions. Reusing a PR source branch needs Force push on that branch; do not bypass protected-target policies.
  • Version boundaries: The Azure DevOps extension and companion GitHub Actions target v2.2, but publish separately. Shared v2.2 behavior applies only after each integration is upgraded; GitHub input names use kebab-case.