As we use tags for the unit test files, they don't run if one does not provide the tags=unit flag to the test execution command. This change adds the description of how one is to do this when running the tests in a shell, as well as how to add it to the VS Code extension.
Co-authored-by: tiloKo <70266685+tiloKo@users.noreply.github.com>
* trust engine config and handelling for vault
* add function for resolving trust engine reference
* refactor
* add basic test
* adapt to new trust engine response format
* remove accidental cyclic dependency
* move trust engine hook config
* refactor by separating code from vault
* move trust engine files to own pkg
* adapt to changes of previous commit
* log full error response of trust engine API
* enable getting multiple tokens from trustengine
* remove comment
* incorporate review comments
* go generate
* update unit tests
* apply suggested changes from code review
* fix unit tests
* add unit tests for config pkg
* make changes based on review comments
* make trust engine token available in GeneralConfig and minor fixes
* fix error logic when reading trust engine hook
* make getResponse more flexible and update logging
* update resource reference format
* improve URL handling
* improve logging
* use errors.Wrap() instead of errors.Join()
* update log messages based on suggestions
* remove trustengine resource ref from Sonar step
---------
Co-authored-by: Keshav <anil.keshav@sap.com>
Co-authored-by: jliempt <>
* Added pagination logic for retrieving projects from Black Duck server
* fixed unit tests for getProject in blackduck
* fixed unit tests for getProject in blackduck
* fixed unit tests for getProject in blackduck
* Update abapAddonAssemblyKitCheck.yaml
remove bullet points as they are not rendered together with markdown
* Update abapAddonAssemblyKitCheck.yaml
* delete trailing space
* go generate
* Fix NPE in utils unstash
* fix test
---------
Co-authored-by: Vijayan T <vijayanjay@gmail.com>
Co-authored-by: Christopher Fenner <26137398+CCFenner@users.noreply.github.com>
* Improve logs of credentialdiggerScan step
* 'Restore step'
* Use dockerhub image for Credential Digger
* Regenerate credentialdiggerScan
* Update docker image tag
* Fix report generation with exportAll
* Update docker image for credentialdiggerScan
* Regenerate credentialdiggerScan step with new docker image
* Dont duplicate step name with log.Entry()
* Refactor RepoURL according to #4639
---------
Co-authored-by: Marcus Holl <marcus.holl@sap.com>
Co-authored-by: Googlom <36107508+Googlom@users.noreply.github.com>
* Remove blue green deployment support for cf native build tools
* Empty for testing
* Remove obsolete dependency
* feedback from code review
* Fix IT's run
* Add test
* chore: switch to new parameter name
Since warnings-ng plugin version 11 the blameDisabled parameter
has been replaced by skipBlames.
To be compatible with Jenkinsfile Runner we put the recordIssues step
into a try/catch, so no exception is thrown and the build fails.
* docs: improve wording
Co-authored-by: Srinikitha Kondreddy <srinikitha.kondreddy@sap.com>
---------
Co-authored-by: Srinikitha Kondreddy <srinikitha.kondreddy@sap.com>
