rosineygp

My main problem is running the job/step locally and not wait to CI steps to validate some change.

My solution is: https://github.com/rosineygp/mkdkr

I can write somethings like this:

  py:
   @$(dkr)
   instance: python:3.8
   run: pip install requests
   export MKDKR_SHELL=python
   run: 'import requests
      r = requests.get(f"https://api.isevenapi.xyz/api/iseven/2/")
      print(r.json())'

When you have a PCI device assigned to two or more VMs you cannot up them at same time... the second will fail because the resource already in use.

This tool handler this kind of "lock" like a switch button.

nice words, thanks!

I have a lot of difficult to explain this. I will improve the docs... maybe record a video.

Switch among Guest VMs organized by Resource Pool

there are a lot of solutions for CI.

I just create a small script and run using make

https://github.com/rosineygp/mkdkr

in another words: https://xkcd.com/927/

Thanks! clojure is really amazing! I will try create something using "pure" clojure or another variation like joker or janet-lang...

Ual, there is a lot before Babashka that I didn't know.

So, I already did code in clojure before this... the main reason was just know how a host language works, not pure clojure... clojure has everything you need with two or more functions to resolve (amazing!!!)

And I tried to learn reading clojure.core... but Is very dificult. the project "make a lisp" helps me with this problem.

I will try do something with Babashka or Joker soon.

Thanks!

Babashka is a nice project (I will try to do something or port it), but I use fleck to learn clojure better... to make lines I have to create a lot of base functions and interop. But fleck is slow :(

Alternative method to install clojure, using "clojure", but without clojure

I had to change CI many times.

From jenkins to gitlab... From travis to github actions...

So I build this small project that helps me to change faster without touch in real CI logic.

https://github.com/rosineygp/mkdkr

I think your problem is bigger than mine, but this kind of approach can help you in the future.

It's a unfinished work.

But It already run in following engines:

- gitlab-ci: https://gitlab.com/rosiney.gp/mkdkr/commits/master - actions: https://github.com/rosineygp/mkdkr/actions - travis: https://travis-ci.org/rosineygp/mkdkr - circle-ci: https://circleci.com/gh/rosineygp/mkdkr/tree/master

The bagdes on README.md show it.

Except for gitlab, you have to write your on .yaml by hand. I not finished the exporters/generators.

After write your Makefile, integrated with a engine isn't a big problem.

Take a look at .travis.yml, .gitlab-ci.yml, .circleci/config.yml and .github/workflows/main.yml they are very similar and dumb, just call all jobs resolved in Makefile.

Now the docs are more clear.

Take a look again

I will try to improve the docs to make it clear.

Thanks to reply. I had no idea about this problem.

But the project is very simples Just try to follow the examples and it will word. Also it's looks like others pipeline system based in yaml.

The next changes will be about docs ;)

The propose is a agnostic pipeline language, that can run in github actions, Jenkins or local. The makefile is a tool that already is used with this propose. Makefile is based in local files or folders .PHONY says to make don't looking for this items on project and just run the block of code