| |
Results |
|
SDA: Post Processing Script Quick Start Tutorial
|
Click Close to dismiss the dialog Click the properties icon to view the input and output properties to the step From the drop down select Output properties Notice the properties OS_VERSION and C_FREE with their respective values Further tasks
|
|
|
|
Serena Deployment Automation Guide
|
You can override the default behavior by entering your own script into the step's Post Processing Script field. A post -processing script can contain any valid JavaScript code. ... 5. Select the source for the artifacts from the Source Config Type drop -down list.
|
|
|
SDA: Post Processing Script Evaluation Getting Started
|
SDA: Post Processing Script Evaluation Getting Started
|
|
|
|
Use of Upload Artifacts step to transfer files from agents back to server drops files
|
Use of Upload Artifacts step to transfer files from agents back to server drops files
|
|
|
20083476.txt
|
it seems there is a bug in Oracle related to how you connect to the DB or run joins. It might be something to look into for your R&D team, i will post the details below from our DBA's, we have changed the settings and the error seems to be gone. SDAPROD, error we are getting.
|
|
|
|
DA: New in 6.2.1 the Property Picker function
|
The following blog post describes a simple but highly effective enhancement that has been introduced in Deployment Automation 6.2.1.
|
|
|
|
SDA: Lines of Interest (LOI) are not highlighted in the relevant log as expected
|
If a process step has a post -processing script associated, and if that script has one or more registered scanners, the lines will not be highlighted in color as expected.
|
|
|
|
DA: Error: An existing connection was forcibly closed by the remote host
|
This is a Tomcat error. This error will occur whenever a thread has a connection open for a long period of time and some problem causes that connection to drop . For example, a network problem or a remote agent crash.
|
|
|
|
DA: An overview of event driven import of component versions
|
Many customers use the simplest method of automating import to occur at build time. The DA plugin for Jenkins (the one that you install into Jenkins), includes several post -build steps including the ability to publish artifacts to DA. This method imports the artifacts from the Build work area, or any directory you specify and creates a new version within DA (you specify the version name - it is easy to use the Jenkins build ID).
|
|
|
|
Creating database views to use for running Deployment Automation reports
|
To create the SQL Views, execute the ddl to create the views in your database according to the steps required for your DBMS. For Oracle and SQL Server view the Serena Central Blog Post . For example, for Derby, use the following steps:
|
|
|
