3 ms·
Thats very true, I used taskfile personally and professionally for a few projects and encoutered some problems I tried to solve with this project. I even tried
by no0dles 5y ago
Thats very true, I used taskfile personally and professionally for a few projects and encoutered some problems I tried to solve with this project. I even tried to contribute there, but it was not that easy, since I am not that fluent in go
- stephanos2k 5y agoI'm curious: what kind of problems?
- no0dles 5y agomaybe problems is the wrong term, lets call it features I was missing. - without docker images in tasks tooling was not always the same on different machines - a docker image that can be used for gitlab ci - caching on CI systems was a huge effort, requiring to specify all .task directories and build directories - limited includes of other build files, no nesting or loops, making project style taskfiles not possible - the cwd of includes is not relative to the reference taskfile and there are some, which are not solved yet in hammerkit, but planned: - detect changes in cwd during commands, for example with `cd ..` - a service definition, allowing to use databases with some healthchecks to detect startup delays - limiting cpu/memory of build steps / limiting tasks that are executed parallel by resource available