FQA

This section provides solutions to common errors you may encounter when installing or using the plugin.

  1. java.lang.NoClassDefFoundError: Could not initialize class com.softbridge.visionbyte.VisionByte

    • Cause: The TeamCity server was not restarted after installing or updating the plugin.

    • Solution

      Restart the TeamCity server

  2. Failed to build patch for build, due to error: java.io.IOException: java.net.SocketTimeoutException

    • Cause: The patch file sent from the TeamCity server to the build agent was not fully transferred within the allowed time limit, resulting in an incomplete patch and a parsing failure. This is a known TeamCity bug, and it typically occurs on servers with limited bandwidth.

    • Solution

      Switch to agent-side checkout to avoid transferring large patch files from the server.

  3. Unable to connect to the server: errorNum = 1: Warning - cannot connect to: http://your-server/repo

    • Cause: The build agent cannot connect to the repository on the TeamCity server.

    • Solution

      • Verify that the repository URL is correct.

      • Ensure the repository service is running and accessible from the agent machine.

  4. Checkout rules are not supported

    • Cause: The VisionByte VCS does not support file mapping, so checkout rules are currently not supported by this plugin when use agent-side checkout.

    • Solution:

      Remove any checkout rules from the VCS root configuration.

Enable Logging

You can configure a dedicated log file for the VisionByte plugin to simplify maintenance and troubleshooting.

  1. Go to Administration → Server Administration → Diagnostics → Logging Presets → + Upload new file.

  2. Upload a custom logging configuration XML file. For example, the following configuration (debug-vbplugin) can be used:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN" monitorInterval="1">
  <Appenders>
    <RollingFile name="VISIONBYTE" fileName="${sys:teamcity_logs}/visionbyte-log/visionbyte.log"
                 filePattern="${sys:teamcity_logs}/visionbyte-log/visionbyte-%d{yyyy-MM-dd}.log.gz">
      <PatternLayout pattern="%d{HH:mm:ss.SSS} %-5level - %msg%n"/>
      <Policies>
        <TimeBasedTriggeringPolicy interval="1" modulate="true"/>
        <SizeBasedTriggeringPolicy size="10 MB"/>
      </Policies>
      <DefaultRolloverStrategy max="7"/>
    </RollingFile>
  </Appenders>

  <Loggers>
    <!-- Plugin-specific logs only -->
    <Logger name="com.softbridge.visionbyte" level="debug" additivity="false">
      <AppenderRef ref="VISIONBYTE"/>
    </Logger>

    <!-- All other logs remain at WARN level or above -->
    <Root level="warn">
      <!-- Optional: configure a root appender -->
    </Root>
  </Loggers>
</Configuration>

  1. Navigate to Diagnostics → Troubleshooting → Debug Logging and set the Active logging preset to debug-vbplugin (the name of the newly added logging configuration file).

  2. The plugin’s dedicated logs will then be available under Diagnostics → Server Logs → visionbyte-log.