Skip to content

Provides name for Auto-Deploy Pipelines

John Skarbek requested to merge jts/name-auto-deploy-piplines into master

What does this MR do?

  • Leveraging workflow rules to name our pipelines, we create the names using variable PIPELINE_TYPE
  • We then set the value of this to AUTO_DEPLOY_BUILD_PIPELINE - this is the same name leveraged in omnibus
    • This is set only if we detect the tag is an auto-deploy specific tag
    • We use an alternate variable name because we need the / in order to properly regex during pipeline creation.
    • This appears to be a limitation to CI: gitlab-org/gitlab#209904 (closed)
  • All other pipeline names will not be changed from their default - this means they will inherit the name of the last commit title
  • Delivery would like to leverage this feature in order to create an easier method of gathering data for creating metrics on traces to track time spent in various processes

Related issues

Addresses: gitlab-com/gl-infra/delivery#2754 (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

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes - n/a - this is a change to CI
  • Documentation created/updated - n/a - this is a change to CI
  • Integration tests added to GitLab QA - n/a - this is a change to CI
  • The impact any change in container size has should be evaluated - n/a - this is a change to CI
Edited by John Skarbek

Merge request reports