Skip to content

Expose `name` and `merge_request_event_type` in serialized json and predefined variables

Shinya Maeda requested to merge add-pipeline-type-key-in-pipeline-entity into master

What does this MR do?

This MR exposes name and merge_request_event_type in serialized json for pipeline entity. This is only BE change and you can find FE change at https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14664.

Here is the conversion table.

Pipeline type pipeline.name pipeline.merge_request_event_type Condition
Pipelines for merge train Merge train pipeline 'merge_train' N/A
Pipelines for merged results Merged result pipeline 'merged_result' pipeline.flags.merge_request_pipeline === true (To be removed in https://gitlab.com/gitlab-org/gitlab-ee/issues/13991)
Pipelines for merge requests (detached) Detached merge request pipeline 'detached' pipeline.flags.detached_merge_request_pipeline === true (To be removed in https://gitlab.com/gitlab-org/gitlab-ee/issues/13991)
Branch pipelines Pipeline undefined pipeline.ref.branch === true
Tag pipelines Pipeline undefined pipeline.ref.tag === true

This MR also exposes the pipeline.merge_request_event_type as CI_MERGE_REQUEST_EVENT_TYPE predefined variable for a customer request.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

Performance and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Shinya Maeda

Merge request reports