Skip to content

Do not collapse build:package:sync logs on non-tag pipelines

Balasankar 'Balu' C requested to merge expand-package-sync-log into master

What does this MR do?

90% of the time when we push a branch to dev, we end up fetching the packages from S3 bucket. I think it makes sense to expand these on branch pipelines so that we can easily reach those URLs(yes, stable branches will be an edge case, but I think we can live with that).

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