Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
schleuder
schleuder
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 101
    • Issues 101
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • schleuder
  • schleuderschleuder
  • Issues
  • #306

Closed
Open
Opened Jan 22, 2018 by georg@georgOwner

CI: Build Docker image only for {master branch,git tags} or remove Docker images on branch delete

We've started recently to build Docker images. As of now, we're already using ~ 1.5 gigabyte of storage to store these. Obviously, this doesn't scale.

Two ideas how to solve this:

  • We only build the image for the master branch or for git tags, if releasing a new version.
  • We remove the Docker image based on a specific branch on branch delete, e.g. if the branch gets merged to master.

I need some input / opinions on this, because I'm currently unsure who is using the Docker images in which way.

Edited Jan 22, 2018 by georg
Assignee
Assign to
3.2.2
Milestone
3.2.2
Assign milestone
Time tracking
None
Due date
None
Reference: schleuder/schleuder#306