melezhik, melezhik@programming.dev
Instance: programming.dev
Joined: 3 years ago
Posts: 12
Comments: 19
Posts and Comments by melezhik, melezhik@programming.dev
Comments by melezhik, melezhik@programming.dev
Example of dsci pipeline - https://forgejo.sparrowhub.io/root/test/src/branch/main/.dsci
I am going to simplify installation method to just single golang binary , coming soon
Hey 👋 and thanks for your interest. Yes it can be self hosted - please read this - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup , right now you need to build your own container image and run it with docker/podman. Please let me know if I can help
just test
just use dedicated alpine image, pretty easy:
https://deadsimpleci.sparrowhub.io/doc/cookbook

In what environment is the CI
By default this is alline:latest docker container , however one can use custom docker images ( to be documented, but let me know if you are interested ), on the demo server , Ubuntu image is used
run_task comes as a part of dsci SDK for Python . What do you mean by build time dependencies? You are free put anything into Python / Bash tasks that are called by run_task function in job file … if you point your repo on demo server I can help you with that …
Update for new users: Just create some repo and add http://127.0.0.1:4000/forgejo_hook to a repo web hook, then create some dsci pipeline and it will gets triggered
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 ."
Feedback are welcome , the project is in very early stage …
You may try out https://github.com/melezhik/sparky which a local / remote task runner with nice front end and scripts could be written on many languages
Yep. Fancy devs watching me coding some Rakulang in nano 😂
Ok. "I am a good FOSS developer"
Thanks, will take a look
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
fair enough, however the intention is to show how one could *create* rules on Sparrow/Raku, not to show rules ... Maybe I should have mentioned that ...
for example this is more interesting example evaluation of net.ipv4.tcp_synack_retries"
regexp: ^^ "net.ipv4.tcp_synack_retries" \s* "=" \s* (\d+) \s* $$
generator: <<RAKU
!raku
if matched().elems {
my $v = capture()[];
say "note: net.ipv4.tcp_synack_retries={$v}";
if $v >= 3 && $v <= 5 {
say "assert: 1 net.ipv4.tcp_synack_retries in [3..5] range"
} else {
say "assert: 0 net.ipv4.tcp_synack_retries in [3..5] range"
}
} else {
say "note: net.ipv4.tcp_synack_retries setting not found"
}
RAKU
sorry, could you please elaborate on "shouldn’t copy" ? thanks
you are seemed to have edited your initial reply - "it should be sysctl.conf not syslog.conf " - anyway thanks for that, now it's fixed, this was just overlook typo

Plugins SDK for dead simple ci engine (yamless pipeline engine for gitea/forgejo) (deadsimpleci.sparrowhub.io)
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 …
Dead Simple CI Introduction (dev.to)
Introduction into Dead Simple CI framework for ci pipelines automation.
Example of dsci pipeline - https://forgejo.sparrowhub.io/root/test/src/branch/main/.dsci
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
Hey everyone! After week of work finally rewrote dsci runner on golang.
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
Hey everyone! After week of work finally rewrote dsci runner on golang.
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
Hey everyone! After week of work finally rewrote dsci runner on golang.
I am going to simplify installation method to just single golang binary , coming soon
Hey 👋 and thanks for your interest. Yes it can be self hosted - please read this - http://deadsimpleci.sparrowhub.io/doc/forgejo-setup , right now you need to build your own container image and run it with docker/podman. Please let me know if I can help
just use dedicated alpine image, pretty easy:
https://deadsimpleci.sparrowhub.io/doc/cookbook
By default this is alline:latest docker container , however one can use custom docker images ( to be documented, but let me know if you are interested ), on the demo server , Ubuntu image is used
run_task comes as a part of dsci SDK for Python . What do you mean by build time dependencies? You are free put anything into Python / Bash tasks that are called by run_task function in job file … if you point your repo on demo server I can help you with that …
Update for new users: Just create some repo and add http://127.0.0.1:4000/forgejo_hook to a repo web hook, then create some dsci pipeline and it will gets triggered
Dead Simple CI - looking for beta testers (deadsimpleci.sparrowhub.io)
Hey! I am building a brand new CI based on top of forgejo/gitea - the thing is to use general purpose programming languages instead of YAML for pipelines. So I have launched a forgejo instance with DSCI runner integrated, where you can find some example pipelines for demo projects - http://forgejo.sparrowhub.io/root
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 ."Feedback are welcome , the project is in very early stage …
Dead Simple CI (deadsimpleci.sparrowhub.io)
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 - Text and Test Anything Protocol (doubletap.sparrowhub.io)
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.
You may try out https://github.com/melezhik/sparky which a local / remote task runner with nice front end and scripts could be written on many languages
Yep. Fancy devs watching me coding some Rakulang in nano 😂