On a related note is there a way to set a configuration to lock down all other configs from building? That is when i trigger the configuration to update all the control scripts I want it to queue any new configurations, wait for any that are running to complete, and then run to completion before opening up to other configuration again.
On a related note is there a way to set a configuration to lock down all other configs from building? That is when i trigger the configuration to update all the control scripts I want it to queue any new configurations, wait for any that are running to complete, and then run to completion before opening up to other configuration again.
http://wiki.pmease.com/display/qb30/Tes ... ble+Agents
The latter question can be solved with a read/write exclusive lock: the configuration updating control scripts can be designed to hold a write lock, while all other configurations using the control scripts can hold a read lock. Once write lock is hold, no read locks can be acquired, and once write lock is released, all read locks can proceed concurrently. This is well explained in below tutorial:
http://wiki.pmease.com/display/qb30/Exc ... rce+Access