mirror of
https://github.com/abapGit/abapGit.git
synced 2025-04-30 20:03:20 +08:00
Docs: Fix image links (#4823)
This commit is contained in:
parent
435bc07150
commit
a92059d059
|
@ -30,17 +30,17 @@ There are currently three possibilities to run abapGit CI:
|
|||
|
||||
Selection screen:
|
||||
|
||||

|
||||

|
||||
|
||||
Result list:
|
||||
|
||||

|
||||

|
||||
|
||||
**2) REST API**
|
||||
|
||||
`POST /sap/zabapgit_ci/run`
|
||||
|
||||
[response.json](/docs/example/response.json)
|
||||
[response.json](example/response.json)
|
||||
|
||||
**3) Schedule job sequence with report `ZABAPGIT_CI_JOB_SCHEDULER`**
|
||||
|
||||
|
@ -52,7 +52,7 @@ A job sequence is created with
|
|||
|
||||
3) Run abapGit CI
|
||||
|
||||

|
||||

|
||||
|
||||
**Check transportable packages**
|
||||
|
||||
|
@ -60,7 +60,7 @@ Optionally you can also let abapGit CI create the repositories in transportable
|
|||
|
||||
To set up a suitable transport landscape on the AS ABAP Developer Edition you need to create a new virtual system in STMS (for example `EXP`, `Virtual export system`). This serves as a dummy export target for transport requests. Next you need create a new transport layer (for example `ZEXP`) and connect the current system and the virtual system with it. Then save and activate the configuration.
|
||||
|
||||

|
||||

|
||||
|
||||
**Prerequisites:**
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user