| 14 May 2024 |
 raitobezarius | It would be nice if someone tried it and had a report | 00:34:11 |
| raitobezarius | Or if we could look the setup of some medium to large OSS project using them | 00:34:24 |
 Qyriad | wait does buildbot actually use xonsh? | 00:34:40 |
| raitobezarius | In reply to @qyriad:katesiria.org
wait does buildbot actually use xonsh? No but it's Python so.... | 00:34:51 |
| Qyriad | sadgska fair | 00:35:01 |
| raitobezarius | Lunaphied was saying "not too far from running custom scripts" | 00:35:10 |
| Qyriad | but xonsh would be way better for a CI system imo | 00:35:13 |
| raitobezarius | I just took it one step ahead | 00:35:15 |
| raitobezarius | In reply to @qyriad:katesiria.org
but xonsh would be way better for a CI system imo I knew you would be proponent | 00:35:25 |
 Lunaphied | In reply to @qyriad:katesiria.org
but xonsh would be way better for a CI system imo Yes | 00:35:28 |
| Lunaphied | We should do this I think | 00:35:33 |
| Qyriad | listen if it didn't have the worst bootstrap ever we would fully support xonsh as the nix builder language x3 | 00:36:01 |
| raitobezarius | So you are saying you should build a new bootstrap path for xonsh | 00:36:21 |
| Qyriad | fear | 00:36:36 |
| Qyriad | I think I would rather try to convince infinisil of lua | 00:36:55 |
| raitobezarius | Back on the topic of CI and compute: I'd be wary of multiplying too many providers at the same time because it makes it hard to maintain them on the long run, I think, if we can have on-demand compute 24/7 for the four major platforms, that's really comfortable and then we can look into additional compute for special tasks if needed | 00:37:43 |
| raitobezarius | (thinking about things like Windows or BSD VMs but that's extremely long term) | 00:38:09 |
 samrose | This is what it one of the main builds of postgresql looks like on cirrus fwiw https://cirrus-ci.com/github/postgresql-cfbot/postgresql | 00:40:04 |
| raitobezarius | I don't see the defn of the CI tasks in the repo | 00:41:36 |
| samrose | In reply to @raitobezarius:matrix.org
I don't see the defn of the CI tasks in the repo it looks like they just mirror to github, and run their own git server | 00:43:21 |
| samrose | https://git.postgresql.org/gitweb/ | 00:43:29 |
| samrose | although some of the cirrus build stuff can be seen at https://github.com/postgres/postgres | 00:44:08 |
| samrose | this page says https://cirrus-ci.org/guide/linux/
For arm_container instances Cirrus CI uses a EKS cluster of Graviton2 instances running in AWS.
| 00:44:47 |
| raitobezarius | OK so container based and it doesn't seem to support dynamic CI targets like we do right now | 00:46:15 |
| raitobezarius | Everything has to be spelled in advance | 00:46:21 |
| samrose | raitobezarius: what are the dynamic targets looking like? | 00:47:13 |
| raitobezarius | Unsure if it's worth the trouble compared to just obtaining an Altra Q80 tbh | 00:47:15 |
| samrose | yeah it may not be | 00:47:23 |
| raitobezarius | In reply to @samrose:matrix.org
raitobezarius: what are the dynamic targets looking like? Just nix-eval-jobs on the flake.nix and generate a task for each hydraJobs | 00:47:43 |
| samrose | ah ok | 00:47:58 |
