Add pipeline parameter for release evidence collection
What does this MR do?
This MR adds pipeline parameter to ::Releases::CreateEvidence service. It's not used at the moment and will be used in the next MR.
Originally I was using just last_pipeline for the commit related to the release.
But when release is being created, new tag get's pushed which starts the new pipeline, and it's empty at the moment of evidence collection.
To solve this problem this MR finds the last pipeline available before tag is being created and passes it to evidence collection.
Extracted from !29255 (closed) which was too big for one piece, so I decided to split it into a few separate MRs.
Related to #32773 (closed)
See also #214245 (closed)
Screenshots
The end result is supposed to work like this: https://www.youtube.com/watch?v=pfRzDvSBIWU
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
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