gCTS & CI/CD in ABAP Cloud: DevOps-Pipeline einrichten

┌─────────────────────────────────────────────────────────────────────┐
│                        Entwicklungslandschaft mit gCTS               │
│                                                                      │
│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐              │
│  │     DEV     │    │     QAS     │    │     PRD     │              │
│  │   System    │    │   System    │    │   System    │              │
│  │  ┌───────┐  │    │  ┌───────┐  │    │  ┌───────┐  │              │
│  │  │ gCTS  │  │    │  │ gCTS  │  │    │  │ gCTS  │  │              │
│  │  │Client │  │    │  │Client │  │    │  │Client │  │              │
│  │  └───┬───┘  │    │  └───┬───┘  │    │  └───┬───┘  │              │
│  └──────│──────┘    └──────│──────┘    └──────│──────┘              │
│         │                  │                  │                      │
│         └─────────┬────────┴────────┬─────────┘                      │
│              Push │                 │ Pull                           │
│                   ▼                 ▼                                │
│           ┌───────────────────────────────┐                          │
│           │        Git Repository         │                          │
│           │   (GitHub / GitLab / Azure)   │                          │
│           └───────────────────────────────┘                          │
└─────────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────────────┐
│                        CI/CD Pipeline für ABAP Cloud                     │
│                                                                          │
│  ┌─────────┐   ┌─────────┐   ┌─────────┐   ┌─────────┐   ┌─────────┐   │
│  │  Code   │   │  Build  │   │  Test   │   │ Quality │   │ Deploy  │   │
│  │  Push   │──▶│  Check  │──▶│  Stage  │──▶│  Gate   │──▶│  Stage  │   │
│  └─────────┘   └─────────┘   └─────────┘   └─────────┘   └─────────┘   │
│       │             │             │             │             │         │
│       ▼             ▼             ▼             ▼             ▼         │
│   Git Push      Syntax &     ABAP Unit      ATC Checks    gCTS Pull    │
│   Trigger       Activation   Tests          Code Review   Transport    │
│                              Integration    Coverage                    │
│                              Tests          Security                    │
└─────────────────────────────────────────────────────────────────────────┘

Transaktion: STRUST

1. SSL Client (Standard) öffnen
2. Zertifikat importieren:
   - GitHub: github.com
   - GitLab: gitlab.com (oder eigene Domain)
3. Zertifikatsliste aktualisieren
4. Speichern

┌──────────────────────────────────────────────────────────────┐
│  Repository Configuration                                      │
├──────────────────────────────────────────────────────────────┤
│  Repository Name:    Z_MY_PROJECT                             │
│  Remote URL:         https://github.com/company/project.git   │
│  Branch:             main                                     │
│                                                                │
│  Authentication:                                               │
│  ● Token-based (recommended)                                  │
│                                                                │
│  Username:           github-service-user                      │
│  Token:              ghp_xxxxxxxxxxxx                         │
│                                                                │
│  vSID (Virtual System ID): DEV                                │
└──────────────────────────────────────────────────────────────┘

CLASS zcl_gcts_setup DEFINITION
  PUBLIC FINAL CREATE PUBLIC.

  PUBLIC SECTION.
    METHODS create_repository
      IMPORTING
        iv_repository_name TYPE string
        iv_remote_url      TYPE string
        iv_branch          TYPE string DEFAULT 'main'
      RAISING
        cx_web_http_client_error.
ENDCLASS.

CLASS zcl_gcts_setup IMPLEMENTATION.
  METHOD create_repository.
    DATA(lo_destination) = cl_http_destination_provider=>create_by_url(
      i_url = |http://localhost:50000/sap/bc/cts_abapvcs/repository| ).

    DATA(lo_client) = cl_web_http_client_manager=>create_by_http_destination(
      i_destination = lo_destination ).

    DATA: BEGIN OF ls_request,
            repository TYPE string,
            url        TYPE string,
            branch     TYPE string,
            role       TYPE string VALUE 'SOURCE',
          END OF ls_request.

    ls_request-repository = iv_repository_name.
    ls_request-url = iv_remote_url.
    ls_request-branch = iv_branch.

    DATA(lv_json) = /ui2/cl_json=>serialize(
      data        = ls_request
      compress    = abap_true
      pretty_name = /ui2/cl_json=>pretty_mode-camel_case ).

    DATA(lo_request) = lo_client->get_http_request( ).
    lo_request->set_header_field( i_name = 'Content-Type' i_value = 'application/json' ).
    lo_request->set_text( lv_json ).

    DATA(lo_response) = lo_client->execute( if_web_http_client=>post ).

    IF lo_response->get_status( )-code <> 201.
      RAISE EXCEPTION TYPE cx_web_http_client_error.
    ENDIF.

    lo_client->close( ).
  ENDMETHOD.
ENDCLASS.

" In SE80 oder über ADT:
" Paket Z_MY_PACKAGE → Properties → gCTS Repository zuweisen

CLASS zcl_customer_test DEFINITION
  FOR TESTING
  RISK LEVEL HARMLESS
  DURATION SHORT.

  PRIVATE SECTION.
    CLASS-DATA:
      mo_environment TYPE REF TO if_cds_test_environment.

    CLASS-METHODS:
      class_setup,
      class_teardown.

    METHODS:
      setup,
      teardown,
      test_create_customer_success FOR TESTING,
      test_create_customer_invalid_email FOR TESTING,
      test_update_customer_status FOR TESTING.
ENDCLASS.

CLASS zcl_customer_test IMPLEMENTATION.
  METHOD class_setup.
    " CDS Test Double Framework für isolierte Tests
    mo_environment = cl_cds_test_environment=>create_for_multiple_cds(
      VALUE #(
        ( i_for_entity = 'ZI_CUSTOMER' )
        ( i_for_entity = 'ZI_ORDER' )
      )
    ).
  ENDMETHOD.

  METHOD class_teardown.
    mo_environment->destroy( ).
  ENDMETHOD.

  METHOD setup.
    mo_environment->clear_doubles( ).
    " Mock-Daten einfügen
    DATA(lt_customers) = VALUE zt_customer_t(
      ( customer_id = '1' name = 'Test GmbH' email = '[email protected]' status = 'A' )
    ).
    mo_environment->insert_test_data( lt_customers ).
  ENDMETHOD.

  METHOD teardown.
    ROLLBACK WORK.
  ENDMETHOD.

  METHOD test_create_customer_success.
    " Given
    DATA(lo_cut) = NEW zcl_customer_service( ).
    DATA(ls_input) = VALUE zs_customer_create(
      name  = 'New Customer'
      email = '[email protected]'
    ).

    " When
    DATA(ls_result) = lo_cut->create_customer( ls_input ).

    " Then
    cl_abap_unit_assert=>assert_not_initial(
      act = ls_result-customer_id
      msg = 'Customer ID should be generated'
    ).
  ENDMETHOD.

  METHOD test_create_customer_invalid_email.
    " Given
    DATA(lo_cut) = NEW zcl_customer_service( ).
    DATA(ls_input) = VALUE zs_customer_create(
      name  = 'Invalid Customer'
      email = 'not-an-email'
    ).

    " When / Then
    TRY.
        lo_cut->create_customer( ls_input ).
        cl_abap_unit_assert=>fail( 'Exception expected' ).
      CATCH zcx_customer_error INTO DATA(lx_error).
        cl_abap_unit_assert=>assert_equals(
          act = lx_error->error_code
          exp = 'INVALID_EMAIL'
        ).
    ENDTRY.
  ENDMETHOD.

  METHOD test_update_customer_status.
    " Given
    DATA(lo_cut) = NEW zcl_customer_service( ).

    " When
    lo_cut->set_customer_status( iv_customer_id = '1' iv_status = 'I' ).

    " Then
    DATA(ls_customer) = lo_cut->get_customer( '1' ).
    cl_abap_unit_assert=>assert_equals(
      act = ls_customer-status
      exp = 'I'
      msg = 'Status should be updated'
    ).
  ENDMETHOD.
ENDCLASS.

"! <p class="shorttext">Customer Service Test Coverage</p>
"! @testing ZCL_CUSTOMER_SERVICE
CLASS zcl_customer_test DEFINITION
  FOR TESTING
  RISK LEVEL HARMLESS  " Wichtig: HARMLESS für CI/CD
  DURATION SHORT.      " Wichtig: SHORT für schnelle Pipelines

┌────────────────────────────────────────────────────────────────┐
│  ATC Check Variant: Z_CICD_CHECKS                               │
├────────────────────────────────────────────────────────────────┤
│                                                                  │
│  Priority 1 (Blocker - Pipeline fails):                        │
│  ☑ Syntax Errors                                                │
│  ☑ Security Vulnerabilities (SQL Injection, XSS)               │
│  ☑ Performance Critical (SELECT without WHERE)                 │
│  ☑ Obsolete Statements (not cloud-ready)                       │
│                                                                  │
│  Priority 2 (Warning - Report only):                           │
│  ☑ Naming Conventions                                           │
│  ☑ Code Style                                                   │
│  ☑ Missing Documentation                                        │
│  ☑ Unused Variables                                             │
│                                                                  │
│  Priority 3 (Info - Ignored in CI/CD):                         │
│  ☐ Spelling Suggestions                                         │
│  ☐ Refactoring Opportunities                                   │
│                                                                  │
│  Exemptions:                                                     │
│  - Test Classes (RISK LEVEL, DURATION checks)                  │
│  - Generated Code (SICF handlers)                              │
└────────────────────────────────────────────────────────────────┘

METHOD call_legacy_function.
  " ATC Exemption für bewusst genutzten Legacy-Code
  "#EC CI_NOCHECK - Legacy-Integration, Migration geplant Q3
  CALL FUNCTION 'Z_LEGACY_FUNCTION'
    EXPORTING
      iv_input = mv_input.
ENDMETHOD.

main (Production)
│
├── release/1.0 ────────────────────────────► PRD
│   │
├── develop ─────────────────────────────────► QAS
│   │
│   ├── feature/US-001-kunde-anlegen ────────► DEV
│   │   │
│   │   └── Merge via Pull Request
│   │
│   └── feature/US-002-material-suche ───────► DEV
│
└── hotfix/fix-calculation ──────────────────► Merge to main & develop

# Am Ende der Pipeline hinzufügen
- name: Notify Slack on Failure
  if: failure()
  uses: slackapi/slack-github-action@v1
  with:
    channel-id: 'C01234567'
    slack-message: |
      :x: *ABAP Pipeline Failed*
      Repository: ${{ github.repository }}
      Branch: ${{ github.ref_name }}
      Commit: ${{ github.sha }}
      <${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|View Details>
  env:
    SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}

- name: Notify Slack on Success
  if: success()
  uses: slackapi/slack-github-action@v1
  with:
    channel-id: 'C01234567'
    slack-message: |
      :white_check_mark: *ABAP Pipeline Successful*
      Repository: ${{ github.repository }}
      Deployed to: ${{ matrix.environment }}
  env:
    SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN }}

METHOD get_repository_logs.
  DATA(lo_client) = create_gcts_client( ).

  DATA(lo_request) = lo_client->get_http_request( ).
  lo_request->set_uri_path(
    |/sap/bc/cts_abapvcs/repository/{ iv_repository }/log| ).

  DATA(lo_response) = lo_client->execute( if_web_http_client=>get ).

  IF lo_response->get_status( )-code = 200.
    rv_logs = lo_response->get_text( ).
  ENDIF.

  lo_client->close( ).
ENDMETHOD.