melezhik

joined 2 years ago
 

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 ...

16
submitted 2 months ago* (last edited 2 months ago) by melezhik@programming.dev to c/programming@programming.dev
 

Introduction into Dead Simple CI framework for ci pipelines automation.

https://dev.to/melezhik/dead-simple-ci-introduction-1jh6

1
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
submitted 2 months ago* (last edited 2 months ago) by melezhik@programming.dev to c/show_and_tell@programming.dev
 

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

 

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

1
Dead Simple CI - looking for beta testers (deadsimpleci.sparrowhub.io)
submitted 3 months ago* (last edited 3 months ago) by melezhik@programming.dev to c/show_and_tell@programming.dev
 

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

So I am looking for beta testers, anyone who wants to try out the dsci - please let me know - so I will create an account for you ( you may find the link to the discord channel at the web site ) and you will start to create and run pipelines for projects you like

[–] melezhik@programming.dev 1 points 3 months ago

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

[–] melezhik@programming.dev 2 points 3 months ago* (last edited 3 months ago)

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 ."

[–] melezhik@programming.dev 2 points 3 months ago

Yep,I will figure out the proper design later , but thanks 😊

[–] melezhik@programming.dev 2 points 3 months ago (2 children)

Oh, sorry for that, changed theme to light , hopefully better now

[–] melezhik@programming.dev 3 points 3 months ago

Feedback are welcome , the project is in very early stage …

20
Dead Simple CI (deadsimpleci.sparrowhub.io)
submitted 3 months ago* (last edited 3 months ago) by melezhik@programming.dev to c/programming@programming.dev
 

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

 

Nice screenshots are attached )

 

Tomtit is a cli task runner when you need to run repetitive tasks / tools around your project. It's similar to make, but with more generic approach, not exactly tied to build tasks only

 

After one Rakulang community member and bio informatics developer mentioned the Nexflow data pipeline framework, I was surprised that Sparky and Sparrow6 eco system could be a good fit for such a type of tasks ...

 

Just create a .env/vars.env file which is not kept in source code, define some Bash variables here with sensitive data and then run sparrowdo cli referencing those variables in this file in a safe way:

—tags password=.env[PASSWORD],token=.env[TOKEN]

  • variables are not exposed in bash history
  • not seen via ps aux
  • variables file gets transferred to remote host over scp
  • file with variables not kept on remote host ( immediately removed after exporting to Sparrowdo scenario )
  • host specific vs default env variables allowed

Safe and simple

[–] melezhik@programming.dev 1 points 1 year ago

The plan is to build the entire system on top of Sparky which is written on Raku and extended by Raku

view more: next ›