Dead simple ci is yamless pipeline engine for gitea/forgejo (using web hooks mechanism). Allowing one to write pipeline in general programming language. DSCI provides SDK allow to write extensions for the engine, the same way using general programming languages . This is an introduction - https://deadsimpleci.sparrowhub.io/doc/bash-plugins with simple examples on Bash and Python, but enough to get started …
- 9 posts
- 18 comments
Joined 3 years ago
Cake day: July 31st, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Introduction into Dead Simple CI framework for ci pipelines automation.
Hey everyone! After week of work finally rewrote dsci runner on golang.
git clone https://github.com/melezhik/dsci-runner.git cd dsci-runner go mod tidy go build -o dsci_runner main.go ./dsci_runner
That means just a single binary install Check it out ! )
Forgejo integrations details are here - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup
Hey everyone! After week of work finally rewrote dsci runner on golang.
git clone https://github.com/melezhik/dsci-runner.git cd dsci-runner go mod tidy go build -o dsci_runner main.go ./dsci_runner
That means just a single binary install Check it out ! )
Forgejo integrations details are here - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup
It uses yaml only for configuration part, but pipeline itself is far more then that . Not sure what do you mean by “middle ground”, could you please elaborate? Thanks
Just added the feature of running jobs on localhost for debugging:
cd .dsci/job_one; docker run -it -v $PWD:/opt/job --entrypoint /bin/bash dsci -c "cd /opt/job/; s6 --task-run ."
Yep,I will figure out the proper design later , but thanks 😊
Oh, sorry for that, changed theme to light , hopefully better now
Feedback are welcome , the project is in very early stage …
Dead simple CI - http://deadsimpleci.sparrowhub.io/ could be thought as an extension to any modern CI system - GitHub/Gitea/Gitlab/Forgejo/you name it , adding to default pipeline mechanism (usually based on yaml) the convenient for programmers use of general programming languages, it uses web hooks and commit statues API to report results back to native CI
Double TAP is lightweight testing framework where users write black box tests as rules checking output from tested “boxes”. Boxes could be anything from http client, web server to messages in syslog. This universal approach allows to test anything with just dropping text rules describing system behavior in black box manner.
Rules are written in formal DSL and could be extended on many programming languages
Tool aims to help with infrastructure audit and testing as well as with validating development environments
- melezhik@programming.devto
1 yearYou may try out https://github.com/melezhik/sparky which is a local / remote task runner with nice front end and scripts could be written on many languages
- 1 year
Yep. Fancy devs watching me coding some Rakulang in nano 😂
Ok. “I am a good FOSS developer”
- melezhik@programming.devto
Thanks, will take a look
- melezhik@programming.devto
nano is the best (imho) for up to medium size files. It’s preinstalled in most Linux boxes , it’s simple and flexible enough, takes a minimal amount of time to learn basic for keys and then use them all the time
Not generator, validator. It validates configuration files . Ansible is not flexible in comparison with Sparrow, you’d need to write more boilerplate code to do the same … Also core ansible modules search is limited by “one line” mode, thus it does not allow to search for example within nested structures, like if we want something in between or in nested blocks, or search for sequences, like when we want to search a sequence of strings, a,b,c,d etc, Sparrow does allow al thatl as it has ranges/sequential/SLN search by design. Sparrow allows to generate check rules in runtime as well, Ansible can’t
Example of dsci pipeline - https://forgejo.sparrowhub.io/root/test/src/branch/main/.dsci