actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update jenkins/valet-custom-transformers-lab.md

Browse Source 
Co-authored-by: j-dunham <j-dunham@github.com>
This commit is contained in:
Begona Guereca
2022-08-22 10:12:10 -07:00
committed by GitHub
parent 62d5394565
commit 5eec128d0a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
jenkins/valet-custom-transformers-lab.md
+1 -1
View File
@@ -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`.