Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2022.1

...

  1. Enable auto-configuration in your Parasoft tool by setting the dtp.autoconfig property to true in the tool's .properties configuration file (also see Auto-configuring Code Analysis and Test Execution Tools). 
  2. Choose Report Center Settings from the settings drop-down menu and click Projects. You can also configure SCM settings globally. See Configuring Parasoft Test for All Projects
  3. Locate and click on your project to access the settings.
  4. Specify SCM settings in the Parasoft Test Field. Specific SCM settings are documented in the Parasoft tools user guides. See your tool's documentation for details. 

...

  1. If not already installed, download and install Git on the DTP host.
  2. Choose a location for the mirror and clone the remote repository:
    Code Block
    git clone --mirror <URL_TO_REMOTE_REPO>
  3. Set up a nightly job to update the mirror repository (e.g.for example, git remote update <URL_TO_REMOTE_REPO>). This could be any automated job, such a cron on Linux or a Jenkins job.
  4. Configure the Parasoft Test Settings for your project to show sources from the mirror repository (see Configuring Parasoft Test Settings for Projects):

...

DTP can track canonical files that appear in different SVN branches if the scontrol.rep.svn.url setting is setting is configured properly. This settings setting specifies the SVN repository URL.

...

When source code cannot be displayed from Source Control System:

  • Ensure that the report.xml file is published to DTP has source control information. Check that <Repositories..> section section is present. If this is not the case, then the Parasoft tool configuration is incorrect.
  • Check the source code panel in an explorer view for important information.
  • Ensure that all repository settings are present in Parasoft Test setting. Credentials and other repository settings are necessary to display source code.
  • Ensure that the source control client is available to DTP and correctly configured. Ensure that the client can access the source code using credentials that are configured for DTP.
  • For some source control systems, such as Git, ensure that the repository is cloned and up - to - date at DTP. An external cron job may be necessary for Git to update the local repository regularly.
  • Verify that your SCM supports modifying, moving, or copying sources during build in order to rule-out disconnecting from the original source control system.