

These parameters are relevant for orchestrator usage and not considered when using the command line option. via a Jenkins library step) or on the command line.

In this case, calling the step is essentially reduced to defining the step name.Ĭalling the step can be done either in an orchestrator specific way (e.g. We recommend to define values of step parameters via. If an image for mavenExecute is configured, and npm packages are to be published, the image must have npm installed. Note: npm's gitignore parser might yield different results from your git client, to ignore a "foo" directory globally use the glob pattern "**/foo". It will use your gitignore file to exclude the mached files from publishing.

To find out what will be published, run "npm publish -dry-run" in the project's root folder. It requires a "package.json" file in the project's root directory which has "version" set and is not delared as "private". Publishing npm projects makes use of npm's "publish" command.

Providing the 'npmRepository' or the 'mavenRepository' parameter(s) is not necessary. If the 'format' option is set, the 'URL' can contain the full path including the repository ID. To upload npm projects, you need a package.json in the project root and set the npmRepository option. To upload MTA projects, you need a mta.yaml in the project root and set the mavenRepository option. To upload Maven projects, you need a pom.xml in the project root and set the mavenRepository option. The uploaded file-type depends on your project structure and step configuration. MTA files will be uploaded to a Maven repository. Supports MTA, npm and (multi-module) Maven projects. Upload build artifacts to a Nexus Repository Manager. Upload artifacts to Nexus Repository Manager Description ¶ Set up a Pipeline-Based ABAP Development and Testing Process Using Git-Enabled Change and Transport System Integrate SAP Cloud Transport Management Into Your CI/CD Pipelineīuild and Deploy SAP Fiori Applications on SAP HANA Extended Application Services, Advanced Modelīuild an SAP Fiori Application and Attach It to a Transport Request on an ABAP Systemīuild and Publish Add-on Products on SAP BTP, ABAP EnvironmentĬontinuous Testing on SAP BTP, ABAP Environment Build and Deploy Hybrid Applications with SAP Solution Managerīuild and Deploy SAPUI5/SAP Fiori Applications on SAP BTPīuild and Deploy SAP Cloud Application Programming Model Applications
