You've already forked sap-jenkins-library
mirror of
https://github.com/SAP/jenkins-library.git
synced 2025-07-17 01:42:43 +02:00
Add stage docu (#2460)
* Add stage docu * Add table to configuration.md * Add comment to clone repo stage * Fix indentation errors * Docu: commitID * fix links
This commit is contained in:
@ -58,12 +58,11 @@ repositories:
|
||||
branch: 'master'
|
||||
- name: '/DMO/SOFTWARE_COMPONENT'
|
||||
branch: 'feature'
|
||||
commitID: 'cd87a3cac2bc946b7629580e58598c3db56a26f8'
|
||||
```
|
||||
|
||||
Using such a configuration file is the recommended approach. Please note that you need to use the YAML data structure as in the example above when using the `repositories.yml` config file.
|
||||
|
||||
!!! note "Commit IDs"
|
||||
CommitIDs will also be supported in the future. While the step already includes the handling of commit IDs, the ABAP Environment system will support this not until a later release.
|
||||
If you want to pull a specific commit, the `commitID` can be specified optionally for a repository.
|
||||
|
||||
## Example: Configuration in the Jenkinsfile
|
||||
|
||||
|
@ -49,12 +49,11 @@ repositories:
|
||||
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.
|
||||
|
||||
!!! note "Commit IDs"
|
||||
CommitIDs will also be supported in the future. While the step already includes the handling of commit IDs, the ABAP Environment system will support this not until a later release.
|
||||
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:
|
||||
|
||||
|
Reference in New Issue
Block a user