3 Commits

Author	SHA1	Message	Date
Christopher Fenner	f78777f784	feat(npm): allow to publish artifact to registry (#2871) ... * add new paraeters * update generated sources * run npm publish * add repositoryUrl parameter * handle registry credentials * rename parameter * handle base64encoding * remove vault reference * make username secret * add publish method * use publish method * use dedicated registry * use dry run * fix * prepend path * fix workdir * move code to npm package * do changes * update dependencies * correct property init * remomve dry-run * regenerate * add mock * add logging * add debug log * dry-run * remove try run * remove append * add debug outut * change * add debug output * changes * cleanup * use different auth property * add credential utils * add debug log outputs * remove auth handling & reuse writeFile * rename * fix debug output * remove comments * update comment * rename function * update docs * update generated files * handle npm ignore * remove commented code * add debug output	2021-07-15 14:46:04 +02:00
Siarhei Pazdniakou	cc66b7cabd	Added createBOM parameter to the npmExecuteScripts step (#2642) ... Co-authored-by: Oliver Nocon <33484802+OliverNocon@users.noreply.github.com>	2021-03-04 10:16:59 +01:00
Marcus Holl	6d5a30683b	[refactor] Relocate npmExecutorMock so that it can be used from pkg (#2472) ... From the current location inside "cmd" the npmExecutorMock cannot be used from any coding inside "pkg". When we would like to re-use the npm functionality we have also to provide tests and this requires having a mock. In order to be able to use the mock from pkg we move the mock from "cmd" to "pkg" into package "npm". With the shift from package "cmd" to "npm" a lot of fields in the mock has been made public.	2021-01-04 12:46:14 +01:00