Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T templates
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tecnalia_robotics-public
  • templates
  • Issues
  • #43
Closed
Open
Created Oct 21, 2021 by Prada Sarasola, Miguel@miguel.pradaDeveloper

Force `ddeploy` options (e.g. image retention)

See related comment.

To discuss whether we want to inject certain options to the ddeploy jobs automatically. The case of the image labels Artifactory uses to cleanup old images is the only use-case I can think of right now.

Implementation-wise, if we force anything using CLI arguments on the call to ddeploy, that will deny the user the ability to set the flag themselves (since CLI takes precedence over YAML in ddeploy).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking