In our organization some of the resources (such as QA machines etc) are shared. Different folks get done at different times and some tests have to be run (during dev and QA) on these machines. Right now, we just skype a message to the team stating "I am going to run some destructive tests on such and such machines - let me know if anyone has an issue". This approach obviously has many issues (what happens if someone missed the message etc.) Apart from maintaining a shared google doc that needs to be constantly updated - is there an easier way that folks use for such coordination?
closed as too broad by gnat, GlenH7, Michael Kohne, Bart van Ingen Schenau, MichaelT Mar 19 '14 at 12:53
There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. If this question can be reworded to fit the rules in the help center, please edit the question.
A central scheduler is the heavy weight way to go but has several advantages.
If you set up a number of machines (or virtual machines) that tests can be run on (or machines can be spun up when a test is required) then you can have a central queue that people can submit jobs to and it can figure out what machines are free and what resources can be made available for them.
The other big option that I would normally recommend you consider is continuous delivery / deployment but from your question I'm guessing that isn't an option at the moment.