mirror of https://github.com/SAP/jenkins-library.git synced 2025-01-18 05:18:24 +02:00

Go to file

* Add credentialdiggerScan metadata

* Integrate new step into piper process

* Add credentialdiggerScan implementation and tests

* Remove duplicated code

* Add doc file for credentialdiggerScan step

* Regenerate metadata

* Fix return type in tests

* Add credentialdiggerScan to CommonStepsTest

* Fix typo

* Improve code style

* Add support for custom rules file in stash

* Regenerate metadata for credentialdiggerScan

---------

Co-authored-by: Sven Merk <33895725+nevskrem@users.noreply.github.com>
Co-authored-by: Anil Keshav <anil.keshav@sap.com>

2023-04-04 16:57:15 +02:00

.github

chore(pipeline): update go-version for linting action (#4213 )

2023-02-03 12:35:57 +01:00

.hooks

chore(go): add pre-commit hook (#1006 )

2019-11-27 21:16:01 +01:00

.pipeline

Update config.yml (#2371 )

2020-11-13 16:51:25 +01:00

.reuse

compliance with reuse (#1910 )

2020-08-11 11:53:42 +02:00

cfg

Deploy mkdocs when merging to master

2018-03-12 09:58:32 +01:00

cmd

Add credentialdiggerScan step (#4141 )

2023-04-04 16:57:15 +02:00

consumer-test

Integration Tests fail - edu.hm.hafner (#3071 )

2021-08-25 20:51:54 +02:00

contrib

Allow to trigger release manually (#1359 )

2020-04-03 16:26:53 +02:00

documentation

Add credentialdiggerScan step (#4141 )

2023-04-04 16:57:15 +02:00

integration

feat(cnbBuild): support Vault general purpose secrets as a binding content source (#4281 )

2023-03-31 09:36:59 +02:00

LICENSES

compliance with reuse (#1910 )

2020-08-11 11:53:42 +02:00

pkg

Improve logging for ABAP steps (#4316 )

2023-04-04 12:46:03 +02:00

resources

Add credentialdiggerScan step (#4141 )

2023-04-04 16:57:15 +02:00

src/com/sap/piper

fix(containerPushToRegistry): Add possibility to copy image from private registry (#4247 )

2023-02-24 15:08:05 +06:00

template

remove !#groovy header

2019-05-23 10:37:28 +02:00

test

Add credentialdiggerScan step (#4141 )

2023-04-04 16:57:15 +02:00

vars

Add credentialdiggerScan step (#4141 )

2023-04-04 16:57:15 +02:00

.codeclimate.yml

chore(ci): add yamllint action (#2774 )

2021-04-22 12:55:35 +02:00

.editorconfig

Add golang implementation for karma tests (#919 )

2019-10-25 14:58:59 +02:00

.gitignore

chore: fix linting issues (#3878 )

2022-07-21 09:04:21 +02:00

.log4brains.yml

chore: prepare setup for future ADRs (#4054 )

2022-11-02 14:30:34 +01:00

.markdownlint.yml

chore(ci): add yamllint action (#2774 )

2021-04-22 12:55:35 +02:00

.yamllint.yml

chore(ci): add yamllint action (#2774 )

2021-04-22 12:55:35 +02:00

config.toml

Add revive config for proper linting

2020-02-26 09:44:18 +01:00

DEVELOPMENT.md

docs(development): Add info about release process (#4005 )

2022-09-27 12:51:57 +02:00

Dockerfile

Upgrade Dockerfile to Go 1.18 (#3845 )

2022-06-22 15:59:47 +02:00

go.mod

build(deps): bump golang.org/x/net (#4254 )

2023-03-01 09:05:33 +01:00

go.sum

build(deps): bump golang.org/x/net (#4254 )

2023-03-01 09:05:33 +01:00

LICENSE

chore(license): update LICENSE text (#2855 )

2021-05-26 09:58:12 +02:00

main.go

Step generation: allow usage of go generate (#1793 )

2020-07-17 08:06:11 +02:00

pom.xml

Bump junit from 1.23 to 1.24 (#3868 )

2022-11-08 15:41:45 +01:00

README.md

fix: markdownlint findings for MD012 (#2383 )

2020-11-16 18:22:38 +01:00

staticcheck.conf

add staticcheck github action (#3605 )

2022-03-07 14:52:20 +01:00

README.md

Project Piper Repository

The Project "Piper" offers default pipelines to easily implement CI/CD processes integrating SAP systems. The corresponding "Shared Library" provides a set of "steps" to build your own scenarios beyond defaults.

User Documentation

If you want to view the User Documentation of Project Piper please follow this Piper Pages Link.

Known Issues

A list of known issues is available on the GitHub issues page of this project.

How to obtain support

Feel free to open new issues for feature requests, bugs or general feedback on the GitHub issues page of this project.

Contributing

Read and understand our contribution guidelines before opening a pull request.