Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
delivery
delivery
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 359
    • Issues 359
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • GitLab.com
  • GitLab Infrastructure Team
  • deliverydelivery
  • Issues
  • #1353

Closed
Open
Opened Nov 19, 2020 by Alessio Caiazza@nolith🔴Developer4 of 4 tasks completed4/4 tasks

autodeploy tagging should tag release-tools

As the first step toward the single pipeline &154, we want to clearly identify the deployment pipeline in release-tools.

Implementation plan

  • rake auto_deploy:tag will be extended to support check mode (probably already supported using dry-run mode)
    • when changes are detected in omnibus or CNG:
      • we will not push the new versions on those repositories,
      • we will tag release-tools with the same version used by release-metadata "#{branch.version.to_minor}.#{branch.tag_timestamp}"
  • a new pipeline will be added, it will only run on release-tools tags
    • it will run rake auto_deploy:tag
    • instead of generating the version from the current auto_deploy branch and the timestamp, it will derive that information from the tag name
Edited Dec 16, 2020 by Alessio Caiazza
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-com/gl-infra/delivery#1353