4 ms·
You probably understand make far better than the average developer. While it may be agnostic, it's not entirely clear what your doing here.
by johnmarcus 7y ago
You probably understand make far better than the average developer. While it may be agnostic, it's not entirely clear what your doing here.
- rosineygp 7y agoI 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 ;)
- rosineygp 7y agoNow the docs are more clear. Take a look again
- johnmarcus 7y agoidk, it just seems like a complicated way to run a command in a docker container. i didn't see any ci/cd pipeline actually taking place or how it integrates with all those services.
- rosineygp 7y agoIt's a unfinished work. But It already run in following engines: - gitlab-ci: https://gitlab.com/rosiney.gp/mkdkr/commits/master https://gitlab.com/rosiney.gp/mkdkr/commits/master - actions: https://github.com/rosineygp/mkdkr/actions https://github.com/rosineygp/mkdkr/actions - travis: https://travis-ci.org/rosineygp/mkdkr https://travis-ci.org/rosineygp/mkdkr - circle-ci: https://circleci.com/gh/rosineygp/mkdkr/tree/master 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.