Skip to content

GitLab

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

Closed
Open
Created May 26, 2025 by Pablo Laciana@placianaOwner

Fix the end of activities instead of checking compatibility between schedulers

ChoicesBuilders are meant to give all the possible choices in each state. However, when building schedulers in SchedulerGenerator we want them to take the same decision with respect to the end of each activity (when they have multiple endings).

Currently, we are checking if the choice is compatible with the current choices. However, it would be more efficient to fix the end of activity first and then generate all the possibilities for each combination of end of activities.

See method compatibleLabel in SchedulerGenerator

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking