All geek questions in one place

Where do the build tools go in the source tree?

In every project I have worked on, I have one or more tactical building tools. They perform a check or checksum or some specific build time task. Often these tools are specific to the project and are written in the language of the project.

Q1. Do you have such tools? Is it the smell of the project that I have these tools?

Q2. Where is the source for such tools in the version control system? Not in the original source, not in the original test. Do you keep the original tools that are first built?

+3
source share
2 answers

  • Yes. Tools help automation. Automation is good. This leads you to the worthy goal of automatic continuous builds. This minimizes grunt work. This minimizes errors. It keeps you sane.

  • Depends on the tool. If this is a specific project, I put it in the build / tools / directory of the project tree. If this is a common tool, I keep a common repository.

Doesn't smell at all.

+7
source

I am really. If they are not mature enough (and most of them will never be), it’s easier for me to save them with the project. Properly maintaining a reusable library is more suitable for me.

. , , . , . , .

+3

Source: https://habr.com/ru/post/1732261/

More articles:


All Articles