We encourage our teams to set their utility scripts as Jenkins jobs (integrated with source control).
- The Jenkins job can have a friendly name, a description, a link to wiki article explaining how it works, and default inputs.
- Troubleshooting wiki articles also link back to the job (_"Getting this error? Try running this job"_)
- We don't need to worry about people having prerequisites on their machines (assuming they are installed on the Jenkins runner). They shouldn't even need to understand the language the script is written in, or how it works.
- You've got the opportunity to integrate and chain jobs together, or trigger them based on events.
- Pretty much everyone knows how to create and run Jenkins jobs
Of course having solved one problem (discoverability and organisation of scripts) you now have another one: Jenkins.