From 213c83162239366b501aec7a9137480144ff02bd Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Tue, 23 Aug 2022 09:25:43 -0700 Subject: [PATCH] Update jenkins/valet-custom-transformers-lab.md --- jenkins/valet-custom-transformers-lab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jenkins/valet-custom-transformers-lab.md b/jenkins/valet-custom-transformers-lab.md index 98dfe65..15654d6 100644 --- a/jenkins/valet-custom-transformers-lab.md +++ b/jenkins/valet-custom-transformers-lab.md @@ -165,7 +165,7 @@ After some research we find that the following action will upload an artifact wi path: path/to/artifact/world.txt ``` -We will build this custom transformer similar to how we built the previous custom transformer. This time, we need to add some additional logic. We would like to automate assigning each of the pipeline's file names to the run script. +We will build this custom transformer similar to how we built the previous custom transformer. This time, we need to add some additional logic. We would like to programmatically assign the file path to junit's test results to our upload action. The challenge is, that we are unsure what `item` represents (what the incoming JSON object looks like from Jenkins). In order to troubleshoot this, you could use some basic ruby to print `item` to the terminal. You can achieve this by adding the following line in the transform method: `puts "This is the item: #{item}"`.