mirror of https://github.com/SAP/jenkins-library.git synced 2025-02-19 19:44:27 +02:00

Go to file

Daria Kuznetsova 38f9e5b7f3

fix(setupCommonPipelineEnvironment): handling tags from scm info (#5219 )

* added check if git branch name starts with refs/

* added check if branch name from jenkins starts with refs/

* added tests

* hardcoded refs/tags to test

* removed hardcode

---------

Co-authored-by: sumeet patil <sumeet.patil@sap.com>

2025-01-09 11:19:26 +01:00

.github

Remove README and CONTRIBUTING files from release 2nd try (#5225 )

2025-01-09 09:08:21 +01:00

.hooks

…

.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

…

cmd

fix(naming): Rename Trust Engine to System Trust (#5217 )

2025-01-07 16:44:59 +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

docs: fix npmExuceteTests documentation formatting issues (#5218 )

2025-01-03 13:28:34 +02:00

integration

Update go version to 1.23 and removed some helper methods in favor of STD library (#5200 )

2024-12-12 17:32:12 +02:00

LICENSES

compliance with reuse (#1910 )

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

pkg

fix(setupCommonPipelineEnvironment): handling tags from scm info (#5219 )

2025-01-09 11:19:26 +01:00

resources

fix(naming): Rename Trust Engine to System Trust (#5217 )

2025-01-07 16:44:59 +02:00

src/com/sap/piper

Update go version to 1.23 and removed some helper methods in favor of STD library (#5200 )

2024-12-12 17:32:12 +02:00

template

…

test

fix(setupCommonPipelineEnvironment): handling tags from scm info (#5219 )

2025-01-09 11:19:26 +01:00

vars

fix(setupCommonPipelineEnvironment): handling tags from scm info (#5219 )

2025-01-09 11:19:26 +01:00

.codeclimate.yml

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

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

.editorconfig

Update go version to 1.23 and removed some helper methods in favor of STD library (#5200 )

2024-12-12 17:32:12 +02:00

.gitignore

refactor(orchestrator): Use singleton in orchestrator package and rename methods (#4639 )

2024-01-09 16:01:15 +05: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

.mockery.yml

chore(mockery): add mockery configuration (#4941 )

2024-06-04 13:40:35 +02:00

.yamllint.yml

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

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

config.toml

…

CONTRIBUTING.md

CONTRIBUTING.md (#5042 )

2024-09-13 14:00:11 +02:00

Dockerfile

Update go version to 1.23 and removed some helper methods in favor of STD library (#5200 )

2024-12-12 17:32:12 +02:00

go.mod

Update go version to 1.23 and removed some helper methods in favor of STD library (#5200 )

2024-12-12 17:32:12 +02:00

go.sum

Updated help from 3.14.2 to 3.14.4 (#5188 )

2024-11-27 13:57:54 +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

chore(deps): update dependency org.jacoco:jacoco-maven-plugin to v0.8.11 (#4792 )

2024-02-02 09:41:04 +01:00

README.md

CONTRIBUTING.md (#5042 )

2024-09-13 14:00:11 +02: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.