7 Commits

Author	SHA1	Message	Date
Stephan Aßmus	7811def7c6	Add technical stage names behind feature toggle (#1933)	2020-08-28 16:11:35 +02:00
Stephan Aßmus	6a71feeafd	Align stage name (#1922) ... * Set env.STAGE_NAME to stageName from params * Revert #1796	2020-08-13 17:01:22 +02:00
Kevin Hudemann	eea0c1f35e	Use npmExecuteEndToEndTests step in Release/Acceptance stage if it is configured (#1813) ... This change enables the use of the new npmExecuteEndToEndTests in the stages release and acceptance if it is configured. If it is not configured, nothing should change.	2020-07-17 13:59:14 +02:00
Daniel Kurzynski	f933788d86	Pass stageName through to steps (#1796)	2020-07-17 13:32:49 +02:00
Florian Wilhelm	ccc77bbc11	Use multicloudDeploy step in Release/Acceptance Stage if it is configured (#1789) ... The multicloudDeploy step is newer and more capable compared to the old steps. For pipelines that don't configure the multicloudDeploy step, nothing should change.	2020-07-13 14:26:26 +02:00
Oliver Nocon	9e539e68ee	Piper pipeline - enhance stages (#755) ... * fill PRVoting stage with content * add prVoting stage incl. tests * add Build stage incl. Tests * add docs pages * add additional unit test stage * add acceptance stage and additional documentation ... * add release stage content * add promote stage * add Security stage, fix defaults for Promote stage * fix issue in doc generation	2019-07-03 10:13:26 +02:00
Oliver Nocon	74366631b5	Project "Piper" Template: framework and structure (#476) ... * Project "Piper" Template: framework and structure This is the first in a series of Pull-Requests to provide a fully functional Pipeline template into the library. This PR contains: * general Pipeline structure incl. tests * Pipeline initialization incl. tests * Hollow pipeline stages incl. tests * first set of default values * add gitUrls to commonPipelineEnvironment * set correct git information on commonPipelineEnvironment	2019-02-05 15:37:59 +01:00