Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • CARA CARA
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 64
    • Issues 64
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CARA
  • CARACARA
  • Merge requests
  • !185

Merged
Created May 27, 2021 by Nicolas Mounet@nimounetDeveloper

Prepare for new expiration model - introduction of MultipleExpiration

  • Overview 7
  • Commits 5
  • Pipelines 3
  • Changes 4

Introducing _ExpirationBase (Expiration base class) and MultipleExpiration classes (to mix different expiration kinds easily), with corresponding tests.

This is a prerequisite needed for the creation of a new Expiration class with a more complex model. As a side product, the MultipleExpiration class simplifies the model generator, removing the now obsolete expiration_blend function.

This MR can also be merged to master, in principle (results are not changed).

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/multiple_expiration