From 0187a746c9197d5447e08ce2be49e3e021aae49b Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Tue, 16 Jul 2019 17:36:38 +0300 Subject: [PATCH] Use stage and phase attempt counters when saving test artifacts Azure Pipelines provide counters for running test jobs, these split into System.StageAttempt and System.PhaseAttempt. Use them to make test artifacts unique. For XML test results we don't need to name them differently as they aren't uploaded as artifacts but rather presented in a separate test pane. Reviewed-By: Florence Blanc-Renaud Reviewed-By: Stanislav Levin --- ipatests/azure/templates/test-jobs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ipatests/azure/templates/test-jobs.yml b/ipatests/azure/templates/test-jobs.yml index 5b0173fdf..9e93886f6 100644 --- a/ipatests/azure/templates/test-jobs.yml +++ b/ipatests/azure/templates/test-jobs.yml @@ -33,4 +33,4 @@ jobs: condition: succeededOrFailed() - template: save-test-artifacts.yml parameters: - logsArtifact: logs-${{parameters.jobName}}-$(Build.BuildId)-$(System.JobPositionInPhase)-$(Agent.OS)-$(Agent.OSArchitecture) + logsArtifact: logs-${{parameters.jobName}}-$(Build.BuildId)-$(System.StageAttempt)-$(System.PhaseAttempt)-$(System.JobPositionInPhase)-$(Agent.OS)-$(Agent.OSArchitecture)