From 895e629e078730ee73ca220b0beff9cd2c652e22 Mon Sep 17 00:00:00 2001
From: Grzegorz Bokota <bokota+github@gmail.com>
Date: Mon, 21 Oct 2024 14:01:44 +0200
Subject: [PATCH] chore: Use `PublishPipelineArtifact` in place of
 `PublishBuildArtifacts` to reduce CI fragility (#1213)

## Summary by Sourcery

CI:
- Replace `PublishBuildArtifacts` with `PublishPipelineArtifact` in the
CI pipeline to enhance stability.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
	- Updated Azure Pipelines configuration for improved artifact handling.
	- Introduced parameters for test path and cache directory.
- Set Python version to 3.11 and architecture to x64 for consistency in
builds.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---
 .azure-pipelines/pyinstaller.yaml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.azure-pipelines/pyinstaller.yaml b/.azure-pipelines/pyinstaller.yaml
index 6bccd3594..7a91078dc 100644
--- a/.azure-pipelines/pyinstaller.yaml
+++ b/.azure-pipelines/pyinstaller.yaml
@@ -19,9 +19,9 @@ steps:
       python  build_utils/create_and_pack_executable.py --no-simple-zip
     displayName: build
 
-  - task: PublishBuildArtifacts@1
+  - task: PublishPipelineArtifact@1
     inputs:
-      pathToPublish: dist2
-      artifactName: execs
+      targetPath: dist2
+      publishLocation: pipeline
   - script: ${{ parameters.test_path }}
     displayName: TestBuild