mirror of https://github.com/SAP/jenkins-library.git synced 2025-03-21 21:27:22 +02:00

* Usage of Communication Scenario 901 (instead 510)

* Stage Defaults ATC - Com.Scen 901

* added missing step in Introduction docu

* Correct Link

* Link adapt 2 - generated

* remove Push ATC system configuration again (as only substep)

* feat: allow uploading multiple boms (#3900)

* WIP: Adapt bom names

* + WIP: Adapt bom filenames

* Upgrade cyclonedx gradle plugin and use cyclonedxBom config parameters

* Fix unit tests - use correct name in bom creation

* Fix pythonBuild bom name

* introduce and use npmBomFilename const

* Introduce and use mvnBomFilename const

* Introduce and use gradleBomFilename const

* Use build-tool names for bom suffix

* + Adapt tests (build tool suffix)

* Use BOM schema version 1.2 in gradleExecuteBuild

* Pin version of cyclonedx-maven-plugin to 2.7.1

* Adapt generated files

* Fix integration tests

* Fix integration tests

* Fix gradle build integration tests

Co-authored-by: Oliver Nocon <33484802+OliverNocon@users.noreply.github.com>

* fix(cnbBuild): Create separate temp folder for each creator call (#3910)

Co-authored-by: Pavel Busko <pavel.busko@sap.com>

* feat(fortifyExecuteScan): new spotcheck flags (#3923)

* feat: improve vulnerability reporting via GitHub issues (#3924)

* feat: improve vulnerability reporting via GitHub issues

* feat: update reports

* chore: add tls cert links

* only write log on error

* chore: update formatting

* chore: update handling of direct dependencies

* chore: fix linting issue

* chore: minor updates

* correct typo

Co-authored-by: Daniel Bernd <93763187+danManSAP@users.noreply.github.com>
Co-authored-by: R. Kloe <55529941+rkloe@users.noreply.github.com>
Co-authored-by: Oliver Nocon <33484802+OliverNocon@users.noreply.github.com>
Co-authored-by: Ralf Pannemans <ralf.pannemans@sap.com>
Co-authored-by: Pavel Busko <pavel.busko@sap.com>
Co-authored-by: sumeet patil <sumeet.patil@sap.com>

2022-08-15 10:56:08 +02:00

4.1 KiB

Raw Blame History

ABAP Environment Pipeline

The goal of the ABAP environment pipeline is to enable Continuous Integration for the SAP BTP, ABAP environment, also known as Steampunk. The pipeline contains several stages and supports different scenarios. The general idea is that the user can choose a subset of these stages, which fits her/his use case, for example running nightly ATC checks and AUnit tests or building an ABAP add-on for Steampunk.

Scenarios

The following scenarios are available.

Continuous Testing

This scenario is intended to be used improve the software quality through continuous checks and testing. Please refer to the scenario documentation for more information.

Building ABAP Add-ons for Steampunk

This scenario is intended for SAP partners, who want to offer a Software as a Service (SaaS) solution on Steampunk. This is currently the only use case for building ABAP Add-ons and, more specifically, the stages "Initial Checks", "Build", "Integration Tests", "Confirm" and "Publish". Please refer to the scenario documentation for more information.

Pipeline Stages

The following stages and steps are part of the pipeline:

Stage	Steps
Init	-
Initial Checks	abapAddonAssemblyKitCheckPV, abapAddonAssemblyKitCheckCVs
Prepare System	abapEnvironmentCreateSystem
Clone Repositories	cloudFoundryCreateServiceKey, abapEnvironmentPullGitRepo
Test	cloudFoundryCreateServiceKey, abapEnvironmentRunATCCheck, abapEnvironmentRunAUnitTest
Build	cloudFoundryCreateServiceKey, abapAddonAssemblyKitReserveNextPackages, abapEnvironmentAssemblePackages, abapAddonAssemblyKitRegisterPackages, abapEnvironmentAssembleConfirm, abapAddonAssemblyKitReleasePackages, abapAddonAssemblyKitCreateTargetVector, abapAddonAssemblyKitPublishTargetVector
Integration Tests	cloudFoundryCreateService
Confirm	-
Publish	abapAddonAssemblyKitPublishTargetVector
Post	cloudFoundryDeleteService

Please navigate to a stage or step to learn more details. Here you can find a step-by-step example on how to configure your pipeline.

4.1 KiB Raw Blame History