1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-14 11:03:09 +02:00
sap-jenkins-library/test/groovy
Marcus Holl 9529954acd Disable tool validation inside neoDeploy and mtaBuild
We know about two issues:

1.) groovy based file systems checks seems to be executed on Jenkins
    master even if there is a node which is dispatched to a slave.
2.) Environment variable contained in the value of a provided
    variable are not expanded. Example: In case we describe neoHome like
    "$JENKINS_HOME/tools/neo" we do not expand $JENKINS_HOME. Hence the
    file exists check for file '$JENKINS_HOME/tools/neo' fails.
2018-03-08 11:23:56 +01:00
..
com/sap/piper Use executeMaven step for artifact versioning (#114) 2018-03-06 13:28:57 +01:00
util add JenkinsEnvironmentRule 2018-02-28 11:54:52 +01:00
ArtifactSetVersionTest.groovy Use executeMaven step for artifact versioning (#114) 2018-03-06 13:28:57 +01:00
ChecksPublishResultsTest.groovy Update ChecksPublishResultsTest.groovy 2018-03-02 10:53:46 +01:00
DockerExecuteTest.groovy Update DockerExecuteTest.groovy 2018-03-02 10:55:27 +01:00
DurationMeasureTest.groovy use new rules 2018-02-28 13:11:09 +01:00
InfluxWriteDataTest.groovy use new rules 2018-02-28 13:11:09 +01:00
MavenExecuteTest.groovy [refactoring] Rule handling 2018-01-29 09:42:23 +01:00
MTABuildTest.groovy Disable tool validation inside neoDeploy and mtaBuild 2018-03-08 11:23:56 +01:00
NeoDeployTest.groovy Disable tool validation inside neoDeploy and mtaBuild 2018-03-08 11:23:56 +01:00
PipelineExecuteTest.groovy use new rules 2018-02-28 13:11:09 +01:00
SetupCommonPipelineEnvironmentTest.groovy Update SetupCommonPipelineEnvironmentTest.groovy 2018-03-02 10:57:50 +01:00
ToolValidateTest.groovy use new rules 2018-02-28 13:11:09 +01:00