Re:Ask HN: How do you organise and discover your team's inte...
by tdumitrescu on Thursday July 05, 2018 @01:39PM
(#17465187)
In Python world, we've had some success using Click (http://click.pocoo.org/) this way, and for SSH-heavy workloads Fabric (http://www.fabfile.org).
Re:Ask HN: How do you organise and discover your team's inte...
by neduma on Thursday July 05, 2018 @01:50PM
(#17465272)
We ssh-heavy workload, we use ansible. We have jenkins master with dokerized slaves where we throw the scripts in dockerized containers
Re:Ask HN: How do you organise and discover your team's inte...
by candreasen on Thursday July 05, 2018 @02:17PM
(#17465488)
This is the most interesting way of doing it I've seen. How would this be configured/the scripts distributed?
Re:Ask HN: How do you organise and discover your team's inte...
by oh_sigh on Friday July 06, 2018 @12:57AM
(#17468962)
Two ways I've done in the past: have a resolver in the master script which knows how to crawl your source tree(s) and detect the appropriate tagging in specific programs, or have each program get registered in a config script that the master reads from.
I live in a world where we're expected to be synced to head in a monorepo, so distribution is easy for me.
Let's say our project is called cob, so typing `cob` would print a help screen of all the tools it knows about. typing 'cob db' would show all of the tools in the db namespace. For simplicity there is only one level of namespaces allowed. Anything under that is a command in that namespace - eg 'cob db recompute_index --column=foo' to recompute an index, 'cob deploy show_live_version --prod' to show whats in prod right now, etc.
If you're doing a task and think a tool might be available, searching through a limited set of tools based on the likely namespace and with simple help text makes it easy to find.