From b548deb8c8730b27627be159808fd8910827bb40 Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Mon, 22 Aug 2022 14:37:55 -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 3720c96..537214f 100644 --- a/jenkins/valet-custom-transformers-lab.md +++ b/jenkins/valet-custom-transformers-lab.md @@ -138,7 +138,7 @@ When you open the file you should see the following changes in the GitHub Action ## Custom transformers for a known step -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. +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`.