Gitly CI/CD Considerations about gitly HOT 6 OPEN

Does CI need to be a YAML document? I know it's fairly standard in other forges, but I always struggle to follow what's happening in these documents and the syntax seems needlessly complicated to me. We already have v run and $tmpl files. I feel like it should be possible to express CI pipeline scripts purely with V.

from gitly.

You're 100% right @Cons-Cat.

Gitly will be using V scripts for CI.

YAML is terrible.

from gitly.

@medvednikov YAML is kind of cool because it is ez to read and write, but missing schema and weird alias/extending syntax makes it hard for this type of target solution.

YAML is "ez" to read and write... and just as "ez" to get wrong.

from gitly.

For now, really quick way to get CI/CD is to allow to edit Git hooks of the remote repo.
I think that can be done easily and it will allow most part of our needs.

With that we can run V scripts or use the act (or other CI/CD tools) for people who want it.

from gitly.

If this is taken seriously caching should be mandatory and prio #1. GitLab is very bad in caching and GitHub makes it kinda ez. Would love to see some MinIO (or V native Object Storage) or Redis built-in solution. No file caching for security and enhanced methods to do dind builds and caching artifacts.

Especially with projects having node_modules or Angular prjects (which stores compiled files in node_modules) caching is quite a pain to setup and use properly.

from gitly.

@medvednikov YAML is kind of cool because it is ez to read and write, but missing schema and weird alias/extending syntax makes it hard for this type of target solution.

I think TOML would be a good choice, or even JSON (but that even harder to read); both have schema support.

from gitly.