I just don't think onedev is good for the job in that case. Jenkins can at least be run outside of the repository as an extension service.
Kind of I suppose. It would be over my head at the moment. You can assign executors to a job, and agents to an executor, but throttling doesn't really solve a schedueling issue.
It's a backward stop-gap imo not worth using if starting from scratch. Real hardware scheduling would be better imo. So user Y's job gets queued after user X's and make more efficient use of the agent service.
Stacking multiple agents on the same machine just consumes more resources that are already expensive. The goal would be to use the same resources and just better schedule use of them.
ChipTuner
npub1qd…3fqm7
2025-03-28 18:08:48
in reply to nevent1q…4amu
Author Public Key
npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7Published at
2025-03-28 18:08:48Event JSON
{
"id": "35d0e1902a5cd4cdce3bfed65a35163e218fb1c76ebfa2ee8481d064949e4bce",
"pubkey": "036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58",
"created_at": 1743185328,
"kind": 1,
"tags": [
[
"e",
"05884b3e3613647b66109cf2cc663e00c9f0a056b9cea7c8be6abf3963552551",
"ws://192.168.18.7:7777/",
"root",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
],
[
"e",
"077aa4a0bec10bc10ec8d8105212210eaa2c4ca1c1c1d365e55924bf53878b10",
"wss://theforest.nostr1.com/",
"reply",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319"
],
[
"p",
"ee9d979e7e1418a9f7472baf82dc96082a0d4251b77bcb170a6ecec93fadff64"
],
[
"p",
"036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58"
],
[
"p",
"dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"wss://theforest.nostr1.com/"
]
],
"content": "I just don't think onedev is good for the job in that case. Jenkins can at least be run outside of the repository as an extension service. \n\nKind of I suppose. It would be over my head at the moment. You can assign executors to a job, and agents to an executor, but throttling doesn't really solve a schedueling issue. \n\nIt's a backward stop-gap imo not worth using if starting from scratch. Real hardware scheduling would be better imo. So user Y's job gets queued after user X's and make more efficient use of the agent service. \n\nStacking multiple agents on the same machine just consumes more resources that are already expensive. The goal would be to use the same resources and just better schedule use of them. ",
"sig": "f1b4c6e335a7236f2bcb7a6d299cb06c4a4d0f77e79ed2be6c2c2d7a52adeca4bbc746b09c5ea791047f57fe166533d4159001923fb4ca9608a02d11a26894eb"
}