From 50e517781723aa54a6adde4718abf120b3f0136f Mon Sep 17 00:00:00 2001 From: Begona Guereca Date: Tue, 23 Aug 2022 09:18:19 -0700 Subject: [PATCH] Update jenkins/valet-custom-transformers-lab.md Co-authored-by: Ethan Dennis --- 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 803595e..22a690c 100644 --- a/jenkins/valet-custom-transformers-lab.md +++ b/jenkins/valet-custom-transformers-lab.md @@ -156,7 +156,7 @@ When you open the file you should see the following changes in the GitHub Action 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`. +After some research we find that the following action will upload an artifact with the junit test results without depending on a third party action. ```yaml - uses: actions/upload-artifact@v3