3 ms·

I am not convinced that 'not using yaml' and then show a visual ui to define ci pipelines is a great selling point. I definitely wouldn't want to define that th

by wdb 4y ago

I am not convinced that 'not using yaml' and then show a visual ui to define ci pipelines is a great selling point. I definitely wouldn't want to define that through a UI. Instead I think high level of testability of such CI pipelines would be. At the moment it always commit and push the change and wait how the pipelines acts, rinse and repeat. If you could run it locally and find out the results would be such a time saver.

Aeolun 4y ago
Onedev still commits it to the repository as a file, so you’re not entirely out of luck there. Running locally is not a thing though. There’s services that do exactly that though (https://dagger.io/ https://dagger.io/, https://earthly.dev/ https://earthly.dev/).
robinshen 4y ago
The UI internally generates a yaml file to store in the repository. For instance OneDev uses this yaml to build itself: https://code.onedev.io/projects/160/files/main/.onedev-buildspec.yml?view-plain=true https://code.onedev.io/projects/160/files/main/.onedev-build... The advantage is that you can get things working quickly while still be able to diff changes, or generate the file with some other tool.