100) tools that use de...">

Technologies for centralized storage and publishing of perl scripts and "small tools"?

My problem:

There are many (> 100) tools that use development teams that are "home". They are sometimes a perl script, or a β€œweb page,” or just something that performs a few small functions. I need to find a way (as part of my work "Middle Tool Manager") to put them in one directory. None of these tools are β€œproduced” in any way.

I need to somehow measure the use of each tool. Downloading or sending the tool should be trivial, as with loading the tool. Must have version control and management.

Is there technology for centrally storing and publishing these small tools?

Does anyone have experience with such prehistoric ventures in other companies?

Additional question ...

What process checks are appropriate? Do you have a dashboard for tools that are built on the server?

I want us to not have unintended consequences from the scenarios. I also want to make sure that the Business Critical suite is identified and supported.

+3
source share
1 answer

We use a web-based interface for SVN for "locally developed" scripts, settings, and small tools.


trac, svn -. , trac - , , .

, , , , , .

+2

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


All Articles