Permissions for testing cookbooks through Travis


#1

Hi,

We want to give cookbooks being run with Travis the ability to pull in
other cookbooks and run rspec tests.

We were thinking something like this. Make each cookbook a client and
give read access to all cookbooks and allow updates for one (we want
to increase the version number for merges). If that’s a good method,
do you know of a quick way to do it? Doing it manually sounds very
tedious. Also open to safer/better alternatives. Thank you!

Best,

Roger