github.com/jaylevin/jenkins-library@v1.230.4/documentation/docs/steps/abapAddonAssemblyKitPublishTargetVector.md (about)

     1  # ${docGenStepName}
     2  
     3  ## ${docGenDescription}
     4  
     5  ## Prerequisites
     6  
     7  * The credentials to access the AAKaaS (Technical Communication User) must be stored in the Jenkins Credential Store
     8  * This step needs an existing Target Vector as well as the scope where it should be published.
     9  * The Target Vector ID is taken from the addonDescriptor in the commonPipelineEnvironment.
    10  * If you run prior to this step the step [abapAddonAssemblyKitCreateTargetVector](https://sap.github.io/jenkins-library/steps/abapAddonAssemblyKitCreateTargetVector), the Target Vector will be created and its ID will be written to the commonPipelineEnvironment
    11  
    12  A detailed description of all prerequisites of the scenario and how to configure them can be found in the [Scenario Description](https://www.project-piper.io/scenarios/abapEnvironmentAddons/).
    13  
    14  ## ${docGenParameters}
    15  
    16  ## ${docGenConfiguration}
    17  
    18  ## ${docJenkinsPluginDependencies}
    19  
    20  ## Examples
    21  
    22  ### Configuration in the config.yml
    23  
    24  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:
    25  
    26  ```groovy
    27  abapAddonAssemblyKitPublishTargetVector(
    28                      targetVectorScope: 'T',
    29                      script: this,
    30                      )
    31  ```
    32  
    33  If the step is to be configured individually the config.yml should look like this:
    34  
    35  ```yaml
    36  steps:
    37    abapAddonAssemblyKitPublishTargetVector:
    38      abapAddonAssemblyKitCredentialsId: 'abapAddonAssemblyKitCredentialsId'
    39  ```
    40  
    41  More convenient ways of configuration (e.g. on stage level) are described in the respective scenario/pipeline documentation.