jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2026-06-19 22:58:55 +02:00
Code Issues Releases Activity

fix(npmExecuteScripts): fix line break for private dependency (#5376)

Browse Source
This commit is contained in:
Ashly Mathew
2025-06-12 15:21:19 +03:00
committed by GitHub
parent 86a00d1128
commit efaca35597
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cmd/npmExecuteScripts_generated.go
+1 -1
View File
@@ -135,7 +135,7 @@ Only the install command uses the detected package manager (npm, yarn, or pnpm).
Rationale: In the Piper environment, using the npm CLI for non-install commands provides sufficient functionality without requiring additional CLI dependencies. Supporting yarn or pnpm for these commands was deemed unnecessary due to lack of added benefit.<br/>
If your project contains multiple package.json files (i.e., multi module projects), install command will be run in every directory where the package.json file is found. One can use ` + "`" + `buildDescriptorList` + "`" + ` or ` + "`" + `buildDescriptorExcludeList` + "`" + ` (more details below) to override the default behaviour.<br/> Currently multimodule pnpm projects are not supported. For such projects , it is necessary to use ` + "`" + `buildDescriptorList` + "`" + ` parameter pointing to package.json in root folder.
### Build with private dependencies from a repository
If your build has scoped/unscoped dependencies from a private repository you can include a .npmrc into the source code repository as below (replace the ` + "`" + `@privateScope:registry` + "`" + ` value(s) with a valid private repo url) :
If your build has scoped/unscoped dependencies from a private repository you can include a ` + "`" + `.npmrc` + "`" + ` into the source code repository as below (replace the ` + "`" + `@privateScope:registry` + "`" + ` value(s) with a valid private repo url) :<br/>
` + "`" + `` + "`" + `` + "`" + ` @privateScope:registry=https://private.repository.com/ //private.repository.com/:username=${PIPER_VAULTCREDENTIAL_USER} //private.repository.com/:_password=${PIPER_VAULTCREDENTIAL_PASSWORD_BASE64} //private.repository.com/:always-auth=true registry=https://registry.npmjs.org ` + "`" + `` + "`" + `` + "`" + `
` + "`" + `PIPER_VAULTCREDENTIAL_USER` + "`" + ` and ` + "`" + `PIPER_VAULTCREDENTIAL_PASSWORD_BASE64` + "`" + ` (Base64 encoded password) are the username and password for the private repository and are exposed are environment variables that must be present in the environment where the Piper step runs or alternatively can be created using : [vault general purpose credentials](../infrastructure/vault.md#using-vault-for-general-purpose-and-test-credentials)`,
PreRunE: func(cmd *cobra.Command, _ []string) error {
resources/metadata/npmExecuteScripts.yaml
+2 -2
View File
@@ -26,8 +26,8 @@ metadata:
### Build with private dependencies from a repository
If your build has scoped/unscoped dependencies from a private repository you can include a .npmrc into the source code
repository as below (replace the `@privateScope:registry` value(s) with a valid private repo url) :
If your build has scoped/unscoped dependencies from a private repository you can include a `.npmrc` into the source code
repository as below (replace the `@privateScope:registry` value(s) with a valid private repo url) :<br/>
```
@privateScope:registry=https://private.repository.com/