Skip to content

Allow asset compilation in auto-deploy pipelines to be controlled by variables

Balasankar 'Balu' C requested to merge autodeploy-compile-assets into master

What does this MR do?

Similar to what was done for omnibus-gitlab in gitlab-org/omnibus-gitlab!4758 (merged), introduce AUTO_DEPLOY_COMPILE_ASSETS variable that acts as a feature flag to decide whether assets need to be compiled or not in auto-deploy pipelines. While we can flip COMPILE_ASSETS and do this for all pipelines if something breaks, handling auto-deploys separately since they can block GitLab.com releases while we properly find the cause of the breakage makes more sense.

Discussion in #2057 (comment 2026586747)

Related issues

#2057 (closed)

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
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Integration tests added to GitLab QA
  • The impact any change in container size has should be evaluated
  • New dependencies are managed with dependencies.io
Edited by Jason Plum

Merge request reports