mirror of
https://github.com/SAP/jenkins-library.git
synced 2024-12-14 11:03:09 +02:00
b6fd507145
In the free wild it is the duty of libraryResource to provide some resource as text and it is the duty of readYaml to parse a text (... would also be possible to read a file instead just parsing text, but that is a different story). In our setup we just forwarded the resource name in libraryResource and reacted on that resource name inside read yaml. There was no yaml parsing at all, the yaml 'as it' was returned. The approach now is much closer to reality. Library resource now provides the text 'behind' the resource and yaml parses it. There is now a real yaml parsing. Read yaml is now not registered explicitly anymore. It is just the readYaml closure which is registerd by default for our tests. |
||
|---|---|---|
| .. | ||
| com/sap/piper | ||
| util | ||
| ArtifactSetVersionTest.groovy | ||
| BatsExecuteTestsTest.groovy | ||
| CheckChangeInDevelopmentTest.groovy | ||
| ChecksPublishResultsTest.groovy | ||
| CloudFoundryDeployTest.groovy | ||
| DockerExecuteOnKubernetesTest.groovy | ||
| DockerExecuteTest.groovy | ||
| DurationMeasureTest.groovy | ||
| InfluxWriteDataTest.groovy | ||
| MavenExecuteTest.groovy | ||
| MTABuildTest.groovy | ||
| NeoDeployTest.groovy | ||
| NewmanExecuteTest.groovy | ||
| PipelineExecuteTest.groovy | ||
| PipelineStashFilesAfterBuildTest.groovy | ||
| PipelineStashFilesBeforeBuildTest.groovy | ||
| PrepareDefaultValuesTest.groovy | ||
| SetupCommonPipelineEnvironmentTest.groovy | ||
| SnykExecuteTest.groovy | ||
| TestsPublishResultsTest.groovy | ||
| ToolValidateTest.groovy | ||
| TransportRequestCreateTest.groovy | ||
| TransportRequestReleaseTest.groovy | ||
| TransportRequestUploadFileTest.groovy | ||