From 5eec128d0a50b7029f0379fbcd2fb1c6b443767c Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Mon, 22 Aug 2022 10:12:10 -0700 Subject: [PATCH] Update jenkins/valet-custom-transformers-lab.md Co-authored-by: j-dunham --- 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 4e4f2ad..6090cfd 100644 --- a/jenkins/valet-custom-transformers-lab.md +++ b/jenkins/valet-custom-transformers-lab.md @@ -136,7 +136,7 @@ When you open the file you should see the following changes in the GitHub Action ## Custom transformers for a known step -In our current scenario, the third-party GitHub action `EnricoMi/publish-unit-test-result-action@v1.7`, that Valet chose to transform for the `junit` step does not meet our needs because our CTO has dictated that our pipelines take no dependencies on third-party actions. We are able to customize the action that we would like Valet to use instead. +Next lets address the third-party GitHub action `EnricoMi/publish-unit-test-result-action@v1.7`, that Valet chose for the `junit` step. This action does not meet our needs because our CTO has dictated that our pipelines take no dependencies on third-party actions. We can customize the action that we would like Valet to use instead. After some research we find that the following scripts will execute our J-unit tests without needing to depend on `EnricoMi/publish-unit-test-result-action@v1.7`.