mirror of
https://github.com/SAP/jenkins-library.git
synced 2024-12-14 11:03:09 +02:00
e61f16abfb
This approach works also in case we are in a subdirectory of the git repo, e.g. in the closure of a dir statement. The decission is delegate to git rather than using internal knowledge about git file names. Well, the directory will be always named '.git', but nevertheless ... May endup in a false positive in case we did not clone a repo AND there is another git repo somewhere upwards in the file system. Maybe some other git repo is located upstairs containing e.g. the jenkins setup. The advantage of working also for subdirectories outweights the disadvantage for the false positive. It is not likely that we have to deal with another git repo upstairs, since the pipeline script is expected to be located in the payload git repo. A phantom repo upstairs looks like a pure academical discussion. |
||
|---|---|---|
| .. | ||
| com/sap/piper | ||
| util | ||
| ArtifactSetVersionTest.groovy | ||
| ChecksPublishResultsTest.groovy | ||
| DockerExecuteTest.groovy | ||
| DurationMeasureTest.groovy | ||
| InfluxWriteDataTest.groovy | ||
| MavenExecuteTest.groovy | ||
| MTABuildTest.groovy | ||
| NeoDeployTest.groovy | ||
| PipelineExecuteTest.groovy | ||
| SetupCommonPipelineEnvironmentTest.groovy | ||
| TestsPublishResultsTest.groovy | ||
| ToolValidateTest.groovy | ||