Checkout the entire git repo for the cloud native trigger.
What does this MR do?
Switched the cng build trigger jobs from using the single script job template, to a regular git checkout with depth of 1
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
The *_VERSION files in the repo are passed along to the trigger to inform it what versions of shell and gitaly to build/tag.
As a result, this isn't just a single-script job.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conforms to the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer -
Has been reviewed by a Database specialist
-
-
EE specific content should be in the top level /eefolder -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
Internationalization required/considered -
If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Rémy Coutable