Linda Siebert
fa95bcc8a9
Match documentation of buildExecute ( #3095 )
...
* Match documentation
* Move comment
* Don't pass containerImageNameAndTag
* Change kaniko tests
* Move code in
Co-authored-by: Oliver Feldmann <oliver.feldmann@sap.com>
2021-09-10 16:25:44 +02:00
Stephan Aßmus
8169d56ef7
Groovy: Load step defaults also from stages section in defaults ( #1943 )
...
Co-authored-by: Christopher Fenner <26137398+CCFenner@users.noreply.github.com>
2020-08-26 15:32:58 +02:00
Daniel Kurzynski
1ee13b358b
Store build tool in commonPipelineEnvironment ( #1645 )
2020-06-09 14:52:03 +02:00
Florian Wilhelm
c490ce9211
Use go-based npmExecuteScripts, mavenBuild in buildExecute ( #1622 )
2020-06-04 17:53:06 +02:00
Sven Merk
46fb4ad5e8
Exchange NonSerializable template engine with GStringTemplateEngine
2019-10-23 13:38:31 +02:00
Oliver Nocon
225cf2485b
Docker Pipeline - fixes and small adoptions ( #779 )
...
* buildExecute: Docker case - minor fixes
* properly care for empty `containerBuildOptions`
* verbose output wrt stashing
* add stage ordinals
* fix wrong script reference
* fix null reference
* adapt stage defaults and allow bats tests
* propagate github org and repo
* add test for bats
2019-07-05 16:32:24 +02:00
Oliver Nocon
5bb6d59753
Add step buildExecute ( #527 )
...
This step should serve as generic entry point in pipelines for building artifacts.
Build principle: build once.
Purpose of the step:
- build using a defined build technology
- store build result for future use in testing etc.
2019-07-02 13:00:36 +02:00
