Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML SRA: Plugin: Groovy plugin issue
SRA: Plugin: Groovy plugin issue
CMS-XML SRA: Agent only install is failing
C:\Users\<username>\AppData\Local\Temp\21\serenara-agent-install\install.with. groovy .xml:8: The following error occurred while executing this line:
CMS-XML SDA/SRA: Tutorial: Creating Your First Serena Deployment Automation Plug-in
In this tutorial you will learn how to create a Deployment Automation plug-in that prints “Hello World!” to the console. The example Groovy and XML files are attached to this solution. Note:
PDF Creating an example plugin: Hello World
1. A directory name to identify the plugin, under which the relevant plugin source and description files will exist 2. A . groovy files contains the source code that describes the actions of the plugin 3. Several .xml files that describe the plugin
CMS-XML SDA: Write your own plugin Getting Started Tutorial
Included reference sections a section on Groovy How to debug the code from an existing plugin
CMS-XML SRA: Where is the temporary file stored on the agent that contains all the commands to run?
The actual plugins code is stored in the agent's folder core\var\plugins. Each folder within core\var\plugins corresponds to the downloaded version of the plugin. If you want to see actual groovy scripts used in the plugin you can start from this folder.
CMS-XML SRA: Create component mapping step fails
udeploy.environments.EnvironmentHelper.createComponentMapping(EnvironmentHelper. groovy :78) at com.urbancode.air.plugin.udeploy.environments.EnvironmentHelper$
CMS-XML KB-SRA 4.5: SRA version / create version plugin causes intermittent Java exception
at com.urbancode.ds.client.AddVersionFilesCommand.beginTransaction( at com.urbancode.ds.client.AddVersionFilesCommand.execute( at groovy :42)
CMS-XML SRA: The Version plug-in steps fail if SRA uses SSO
at groovy :34) Add status step fails with the following exception: Adding status stable to version 1 on component 2
CMS-XML SRA 4.5.1: 7Zip-JBinding UnsatisfiedLinkError using the 4.5.1 7Zip plugin
at net.sf.sevenzipjbinding.SevenZip.openInArchive( at net.sf.sevenzipjbinding.SevenZip$ Source) at groovy :48)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs