Stephan Aßmus 56699ab019 Run artifactPrepareVersion in maven container if necessary (#1634) ... * The metadata for artifactPrepareVersion-go specifies a container for when the buildTool is maven. * The alias to 'mavenExecute' was removed. The problem with this is that when a section containers is included in the metadata, dockerImage will always be picked up from mavenExecute, the conditional dependency on buildTool will not even be considered. Parameters such as m2Path, projectSettingsFile and globalSettingsFile should be configured in general/maven if necessary. * When the step ends up being executed within dockerExecuteOnKubernetes, we need to preserve the .git folder. This folder would normally be excluded by the default excludes of the stash step. There was already a comment that suppressing this behavior by passing useDefaultExcludes: false was problematic (unfortunately without going into details), so I've added a new parameter to dockerExecute and dockerExecuteOnKubernetes named stashNoDefaultExcludes (note the reverted meaning to ease preserving the default behavior when this parameter is not provided). This parameter is passed to piperExecuteBin from the artifactPreferVersion groovy wrapper.		2020-06-08 17:08:05 +02:00
..
build-tools.md	Run artifactPrepareVersion in maven container if necessary (#1634)	2020-06-08 17:08:05 +02:00
cloud-qualities.md	Add a link to Jenkins declarative pipeline docs (#1194)	2020-02-21 14:10:11 +01:00
introduction.md	Fix typo in docs (#1586)	2020-05-25 15:12:47 +02:00