[WIP] feat : Add logic in manager to monitor Pending PipelineRuns and run them

[rohanKanojia]

Description

⚠️ This is still a work in progress. It's only created to gather early feedback and decide on some unclear implementation aspects. Once I get more clarity I'll refine it further and add unit tests.

• Add a method in manager.go to list all PipelineRuns in Pending status every 5 seconds
  • As of now, all pending PipelineRuns will be started immediately.

This PR is based on my discussion with @albfan :

• list pipelineruns in PENDING
• evaluate which can be started (by now all of them, later depending on non busy machines)
• do something when each ends (by now nothing at end, mark machines as ready again)
• Add some control on machines to confirm they are not busy (just if someone start a job manually without eventmanager)
• inspect too annotations or labels on running pipelineruns, and attach a listener for them (to confirm when they finish)
• on pipelinerun finish, free related machines (in internal status from eventmanager)
• design the data structure for exising machines and how to decide what machines need each test (e.g.)
  • mac needs mac-brno1 to build and mac-brno4 to test
  • windows needs windows-blr to build and windows-1-brno to test
  • linux uses linux-1-brno to build and test (it builds on a container)

Signed-off-by: Rohan Kumar rohaan@redhat.com

[adrianriobo]

I guess it is too early but this logic (hard part of the logic) should be on its own package...the manager should kept as much clean as possible

[rohanKanojia]

I apologize for the messy state of this PR. It's still in a poc-ish state.

Let me at least move this portion to a separate package.

[adrianriobo]

yeah yean no need to apologies, I saw the WIP you can keep it as much messy as you want till it works and you start to cleanup it up.

Just went through it and added the comment. Feel free to manage it whenever you want not right now

[rohanKanojia]

I've reorganized the code into a separate package named autoscheduling (not 100% sure about the naming)

pkg/manager/autoscheduling
├── baremetal.go                      # Handles connection and status retrieval for QE lab instances  
└── pipelinerun_manager.go            # Manages status updates for Pending/Completed PipelineRuns  

Let me know your thoughts on the package structure and naming.

[adrianriobo]

Yeah that seems perfect, may I even reduce the name to scheduling or scheduler and then inside the type of resource scheduled in this case pipelines but totally up to you.