Skip to content

Print GitLab component SHAs at end of every build in triggered pipeline

Balasankar 'Balu' C requested to merge print-component-shas-cache into master

What does this MR do?

Add build:component_shas rake task to *build_package CI anchor so that it gets run on all package builds. Right now, it is not being run for update-trigger-package-cache job (which updates our cache archives), so we have no way to know which refs of the components was used in the cache. This MR fixes it.

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by Balasankar 'Balu' C

Merge request reports