mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-04-23 12:19:04 +02:00
e83a380c09
* Update configuration.md * Update build.md * Update cloneRepositories.md * Update integrationTest.md * Update post.md * Update prepareSystem.md * Update publish.md * Update configuration.md * Update configuration.md * Update introduction.md * Update build.md * Update CAP_Scenario.md * Update CAP_Scenario.md * Update abapEnvironmentAddons.md * Update abapEnvironmentAddons.md * Update abapEnvironmentTest.md * Update changeManagement.md * Update Readme.md * Update Readme.md * Update introduction.md * Update abapEnvironmentAssembleConfirm.md * Update abapEnvironmentAssemblePackages.md * Update abapEnvironmentCheckoutBranch.md * Update abapEnvironmentCloneGitRepo.md * Update abapEnvironmentCreateSystem.md * Update abapEnvironmentPullGitRepo.md * Update abapEnvironmentRunATCCheck.md * Update cloudFoundryCreateService.md * Update cloudFoundryCreateSpace.md * Update cloudFoundryDeleteSpace.md * Update mtaBuild.md * Update neoDeploy.md * Update protecodeExecuteScan.md * Update uiVeri5ExecuteTests.md * Update guidedtour.md * Update index.md * Update configuration.md * Update guidedtour.md * Update configuration.md * Update build.md * Update CAP_Scenario.md * Update TMS_Extension.md * Update TMS_Extension.md * Update abapEnvironmentAddons.md * Update abapEnvironmentTest.md * Update Readme.md * Update Readme.md * Update cloudFoundryDeploy.md * Update influxWriteData.md * Update neoDeploy.md * Update CAP_Scenario.md * Update TMS_Extension.md * Update Readme.md * Update Readme.md * Update guidedtour.md * Update guidedtour.md * Update guidedtour.md * Update configuration.md Co-authored-by: Thorsten Duda <thorsten.duda@sap.com>
100 lines
3.9 KiB
Markdown
100 lines
3.9 KiB
Markdown
# ${docGenStepName}
|
|
|
|
## ${docGenDescription}
|
|
|
|
## Prerequisites
|
|
|
|
A SAP BTP, ABAP environment system is available.
|
|
On this system, a [Communication User](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/0377adea0401467f939827242c1f4014.html), a [Communication System](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/1bfe32ae08074b7186e375ab425fb114.html) and a [Communication Arrangement](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/a0771f6765f54e1c8193ad8582a32edb.html) is setup for the Communication Scenario "SAP BTP, ABAP Environment - Software Component Test Integration (SAP_COM_0510)". This can be done manually through the respective applications on the SAP BTP, ABAP environment system or through creating a service key for the system on Cloud Foundry with the parameters {"scenario_id": "SAP_COM_0510", "type": "basic"}. In a pipeline, you can do this with the step [cloudFoundryCreateServiceKey](https://sap.github.io/jenkins-library/steps/cloudFoundryCreateServiceKey/).
|
|
|
|
## ${docGenParameters}
|
|
|
|
## ${docGenConfiguration}
|
|
|
|
## ${docJenkinsPluginDependencies}
|
|
|
|
## Example: Configuration in the config.yml
|
|
|
|
The recommended way to configure your pipeline is via the config.yml file. In this case, calling the step in the Jenkinsfile is reduced to one line:
|
|
|
|
```groovy
|
|
abapEnvironmentPullGitRepo script: this
|
|
```
|
|
|
|
If you want to provide the host and credentials of the Communication Arrangement directly, the configuration could look as follows:
|
|
|
|
```yaml
|
|
steps:
|
|
abapEnvironmentPullGitRepo:
|
|
repositoryNames: ['/DMO/GIT_REPOSITORY']
|
|
abapCredentialsId: 'abapCredentialsId'
|
|
host: '1234-abcd-5678-efgh-ijk.abap.eu10.hana.ondemand.com'
|
|
```
|
|
|
|
However, we recommend to use a dedicated file, e.g. `repositories.yml` to specify the repositories to be pulled:
|
|
|
|
```yaml
|
|
steps:
|
|
abapEnvironmentPullGitRepo:
|
|
repositories: 'repositories.yml'
|
|
abapCredentialsId: 'abapCredentialsId'
|
|
host: '1234-abcd-5678-efgh-ijk.abap.eu10.hana.ondemand.com'
|
|
```
|
|
|
|
The associated config file, e.g. `repositories.yml` could look as follows:
|
|
|
|
```yaml
|
|
repositories:
|
|
- name: '/DMO/GIT_REPOSITORY'
|
|
branch: 'master'
|
|
- name: '/DMO/GIT_REPO'
|
|
branch: 'master'
|
|
commitID: 'cd87a3cac2bc946b7629580e58598c3db56a26f8'
|
|
```
|
|
|
|
It is optional to provide a branch. However, if you also want to use this file for the abapEnvironmentCheckoutBranch step it is recommended to follow the above structure.
|
|
If you want to pull a specific commit, the `commitID` can be specified optionally for a repository.
|
|
|
|
If you want to read the host and credentials from the cloud foundry service key of the respective instance, the configuration could look as follows:
|
|
|
|
```yaml
|
|
steps:
|
|
abapEnvironmentPullGitRepo:
|
|
repositoryNames: ['/DMO/GIT_REPOSITORY']
|
|
cfCredentialsId: 'cfCredentialsId'
|
|
cfApiEndpoint: 'https://test.server.com'
|
|
cfOrg: 'cfOrg'
|
|
cfSpace: 'cfSpace'
|
|
cfServiceInstance: 'cfServiceInstance'
|
|
cfServiceKeyName: 'cfServiceKeyName'
|
|
```
|
|
|
|
## Example: Configuration in the Jenkinsfile
|
|
|
|
It is also possible to call the steps - including all parameters - directly in the Jenkinsfile.
|
|
In the first example, the host and the credentialsId of the Communication Arrangement are directly provided.
|
|
|
|
```groovy
|
|
abapEnvironmentPullGitRepo (
|
|
script: this,
|
|
repositoryNames: ['/DMO/GIT_REPOSITORY'],
|
|
abapCredentialsId: 'abapCredentialsId',
|
|
host: '1234-abcd-5678-efgh-ijk.abap.eu10.hana.ondemand.com'
|
|
)
|
|
```
|
|
|
|
In the second example, the host and credentialsId will be read from the provided Cloud Foundry service key of the specified service instance.
|
|
|
|
```groovy
|
|
abapEnvironmentPullGitRepo (
|
|
script: this,
|
|
repositoryNames: ['/DMO/GIT_REPOSITORY', '/DMO/GIT_REPO'],
|
|
abapCredentialsId: 'cfCredentialsId',
|
|
cfApiEndpoint: 'https://test.server.com',
|
|
cfOrg: 'cfOrg',
|
|
cfSpace: 'cfSpace',
|
|
cfServiceInstance: 'cfServiceInstance',
|
|
cfServiceKeyName: 'cfServiceKeyName'
|
|
)
|
|
```
|