![]() Let me take the example of our "build" Pipeline. We don't have 1 Jenkinsfile with 1k lines for 70 jobs, but a whole separate repo containing Jenkinsfiles with multiple of those Files at ~1k lines and those run combined the 70 jobs. I really don't want to rant about the article, but there is a saying in Germany "Wie man in den Wald hinein ruft, so schallt es heraus", roughly translated "The way you scream into the Forrest, it's going to echo back" and this article has many open points that give a lot of attack surface and is written very provocative. Also, his obsessive hate on JSON for configs isn't helping his argument since it's clearly a biased option, especially if he could use something like an JSON shema or JSONC (which is valid for package.json) to solve all his addressed issues in the article he linked inside the text. Which leads me to believe that the Author does not know what the file is supposed to do. The article totally does not mention these things at all. And not a absolutism about how to do things only ONE way ![]() Concern of seperation, package.json for the JS part and a make file for native sub packages, because everyone can agree gyp is not nice.Node projects used to come with `make` files, but that increased the barrier of entry and also did not necessarily work cross-platform, there is a reason cmake exists.A package.json allows you to trigger post-install scripts, you could write some tool to do this with make, but it's not really something you want to add manually to every project you create.You don't write your build script in a package.json you trigger your javascript build script from it (or use task runner like gulp etc.) or a command with the package's environment (node_modules).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |