melezhik

joined 2 years ago
sorted by: new top controversial old
9
Plugins SDK for dead simple ci engine (yamless pipeline engine for gitea/forgejo) (deadsimpleci.sparrowhub.io)
submitted 2 weeks ago* (last edited 2 weeks ago) by melezhik@programming.dev to c/programming@programming.dev
0 comments fedilink
 

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

15
Dead Simple CI Introduction (dev.to)
submitted 3 weeks ago* (last edited 3 weeks ago) by melezhik@programming.dev to c/programming@programming.dev
0 comments fedilink
 

Introduction into Dead Simple CI framework for ci pipelines automation.

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

Dsci runner migrated to golang in c/programming@programming.dev
5
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
submitted 1 month ago* (last edited 1 month ago) by melezhik@programming.dev to c/show_and_tell@programming.dev
0 comments fedilink
 

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

4
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
 

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

6
Dsci runner migrated to golang (deadsimpleci.sparrowhub.io)
 

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

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 1 points 1 month ago

I am going to simplify installation method to just single golang binary , coming soon

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 2 points 1 month ago (1 children)

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

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 1 points 1 month ago

just test

just use dedicated alpine image, pretty easy:

https://deadsimpleci.sparrowhub.io/doc/cookbook

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 1 points 1 month ago* (last edited 1 month ago)

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

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 1 points 1 month ago* (last edited 1 month ago) (2 children)

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 …

Dead Simple CI - looking for beta testers in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 3 points 1 month ago

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 in c/show_and_tell@programming.dev
[–] melezhik@programming.dev 3 points 1 month ago

Actually just enabled self registration , no need to ask me, but still will be happy to see anyone in discord )

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

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

Dead Simple CI in c/programming@programming.dev
[–] melezhik@programming.dev 1 points 1 month 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

Dead Simple CI in c/programming@programming.dev
[–] melezhik@programming.dev 2 points 1 month ago* (last edited 1 month 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 ."

Dead Simple CI in c/programming@programming.dev
Dead Simple CI in c/programming@programming.dev
20
Dead Simple CI (deadsimpleci.sparrowhub.io)
submitted 1 month ago* (last edited 1 month ago) by melezhik@programming.dev to c/programming@programming.dev
4 comments fedilink
 

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

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

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

3
Concat CSV files with Sparky plugin (gist.github.com)
 

Nice screenshots are attached )

4
Tomtit - simple cli task runner with a lot of plugins (github.com)
 

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

6
Data pipelines with Rakulang and Sparky (github.com)
 

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

4
How to pass sensitive data to sparrowdo scenario (gist.github.com)
submitted 6 months ago* (last edited 6 months ago) by melezhik@programming.dev to c/rakulang@programming.dev
0 comments fedilink
 

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

view more: next ›