zlacker

[parent] [thread] 3 comments
1. joachi+(OP)[view] [source] 2025-02-17 18:17:58
For me the issue to be solved is how to easily get the team to run the tool. Some focus should be on integrating build tools.

When I or a team member do gradle build, npm build or cargo build or similar on a fresh checkout the tool should ask to be installed.

replies(2): >>autarc+me >>DrBenC+f12
2. autarc+me[view] [source] 2025-02-17 19:49:40
>>joachi+(OP)
That is what mise from the same author is for. It lets you define per-project sets of tools with specific versions (including languages). I find it quite useful and I'm planning to get my team at work to adopt it once I get some round tuits.
3. DrBenC+f12[view] [source] 2025-02-18 14:01:45
>>joachi+(OP)
I would use a wrapper sh script that checks for the tool and prompts an install, basically how Java projects include maven or gradle into a repo
replies(1): >>hv42+QC2
◧◩
4. hv42+QC2[view] [source] [discussion] 2025-02-18 16:45:24
>>DrBenC+f12
One of the goal of hk is to be used with mise (https://mise.jdx.dev/dev-tools/)

mise supports an experimental bootstrapping feature: it can download itself and install the tools required for the project.

See https://mise.jdx.dev/cli/generate/bootstrap.html and https://mise.jdx.dev/continuous-integration.html#bootstrappi...

[go to top]