Hi there jmash. How did you copy existing config with a new name, through groovy script? I've tried using the sync config step, and there's not a way to change the name of the new config. I had a variable for the new config, but it always uses the default value of that variable

Please help
Thank you!

Below script will do the work:

groovy:

def existingConf = system.configurationManager.get("path/to/existing/conf")
def copiedConf = system.configurationManager.copyAsNew(existingConf, false)
def newParent = system.configurationManager.get("path/to/new/parent")

copiedConf.parent = newParent
copiedConf.name = "new name"
system.configurationManager.save(copiedConf);

To copy configuration recursively:

groovy:

import com.pmease.quickbuild.persistence.SessionManager;

SessionManager.openSession();
try {
  def existingConf = system.configurationManager.get("path/to/existing/conf")
  def copiedConf = system.configurationManager.copyAsNew(existingConf, true)
  def newParent = system.configurationManager.get("path/to/new/parent")

  copiedConf.parent = newParent
  copiedConf.name = "new name"
  system.configurationManager.save(copiedConf, true);
} finally {
  SessionManager.closeSession();
}

Forget to mention that to make this script working, you will need upgrade to QB 7.0.23

Hey Robin,

Thanks for the code above. I have one question though. In "Execute Script" steps, some internal objects from Quickbuild are always available, like: configuration, system, logger, etc...

While coding as a separate jar plugin, what would be the equivalent call to them ?

Something like:

On groovy ----------------------------- Inside external jar that is a QB plugin
logger ----------------------------- Context.getLogger()
system ----------------------------- ?
configuration ------------------------- Context.getConfiguration() or Quickbuild.getCacheManager().getConfigurations() or ?

I'm asking this as some1 who trying to do what the code above does, but packed in a plugin instead of a step.

Thanks and Regards,
Mauro

com.pmease.quickbuild.Context will contain context of current executing builds, such as logger, build, configuration, etc. The system object can be retrieved by calling QuickBuild.getInstance().