SparrowCI VS kcl

Self-hosted SparrowCI supports GitTea integration - https://github.com/melezhik/SparrowCI/blob/main/reporters/gitea.yaml , now it’s just sending back commit statues ( after CI build finished ) , but let me know if you need anything else. I tested it on my self-hosted installation and it works well.

Hi! Thanks for asking. If you mean SparrowCI pipelines then this is - https://github.com/melezhik/SparrowCI

You can try out SparrowCI (https://github.com/melezhik/SparrowCI) -it’s simple and could be self-hosted. It builds on docker images, so if you spin up an SparrowCI on arm64 host you should be probably good. It’s not possible to have 3 separate CI pipelines but you can organize repo pipeline in such a way that it’s split by 3 or many tasks to cover different parts of your system.

Keep building my own free CI service extendable by many languages including Python, please check out Python examples here - https://github.com/melezhik/SparrowCI/tree/main/examples/python

This is neat, guys! I've recently created a similar tool - https://github.com/melezhik/SparrowCI/blob/main/go_support.md , but maybe with a bit different approach, however maybe our tools could be integrated somehow ?

That makes SparrowCI extremely flexible CICD system in comparison with existing solutions (GitHub Actions, Ado Pipelines, GitLab, CircleCI ). The service runs for free now. Try it out! Some examples for popular languages (Python/Ruby/Powershell,Bash,GoLang) could be found here - https://github.com/melezhik/SparrowCI/tree/main/examples

More examples for Ruby could be found here - https://github.com/melezhik/SparrowCI/tree/main/examples/ruby

KCL: A declarative configuration and policy programming language implemented by Rust, which improves the writing of a large number of complex configurations through mature programming language technology and practice, and is committed to building better modularity, scalability and stability around configuration, simpler logic writing, fast automation and good ecological extensionally.

Rust Ver. here

Have you considered using a different language for templating? this could be a BIG selling point. Some good ones are cue-lang (though I haven't seen support for rust), kcl or nickel-lang.

We usually use KCL as the DSL（ https://github.com/KusionStack/KCLVM ）Build a user interface abstraction (masking the Kuberetes concept that developers do not want to understand) and build different UIs based on this abstraction (it can be an IDE interface, a WebUI, or a CLI), which is very flexible and can quickly respond to the increasing demand for UI changes from developers. Alternatively, another approach is to quickly modify YAML through KCL's Mutation capability (different teams can use KCL to write different namespace conditions). And KCL can be combined with ArgoCD to achieve better results

Website: https://kcl-lang.io/

Sure, the IDE/Editor extension based on the kcl-language-server issue is here: https://github.com/KusionStack/KCLVM/issues/513