Having this both as a direct REST call and as a true/false parameter to the configuration delete REST call would be a really good enhancement. Especially if it's made available in the 3.1.x release as that would help us clean up our build machines as we transition them from 3.1.x to 5.0.x.
Description
Having this both as a direct REST call and as a true/false parameter to the configuration delete REST call would be a really good enhancement. Especially if it's made available in the 3.1.x release as that would help us clean up our build machines as we transition them from 3.1.x to 5.0.x.
Will add an option to delete workspaces when delete configurations in QB5 via RESTful API. For other cases, such as deleting configuration workspace separately, this is quite easy by writing some groovy script. For instance to delete workspace of exisitng configuration "root/test", do the following:
groovy:
def testConf = system.configurationManager.get("root/test");
for (each in grid.allNodes) {
def workspace = each.getWorkspaceDir(testConf.id);
each.deleteDir(workspace);
}
Robin Shen[26/Sep/13 12:34 AM]
Will add an option to delete workspaces when delete configurations in QB5 via RESTful API. For other cases, such as deleting configuration workspace separately, this is quite easy by writing some groovy script. For instance to delete workspace of exisitng configuration "root/test", do the following:
groovy:
def testConf = system.configurationManager.get("root/test");
for (each in grid.allNodes) {
def workspace = each.getWorkspaceDir(testConf.id);
each.deleteDir(workspace);
}
New Feature
Resolved
Major
REST: remove workspace from active nodes
groovy:
def testConf = system.configurationManager.get("root/test");
for (each in grid.allNodes) {
def workspace = each.getWorkspaceDir(testConf.id);
each.deleteDir(workspace);
}