Best Practices for JDisc Upgrades and Test Job Execution

1. Purpose

This document outlines best practices for managing JDisc upgrades and executing Test jobs to ensure compatibility, minimise disruption, and maintain efficient job execution.

2. JDisc Upgrade Notifications

Best Practice: Notify Syncfish before upgrading JDisc.

  • Advise Syncfish in advance of any planned JDisc upgrade.

  • Allow Syncfish sufficient time to test the new version and verify compatibility before the upgrade is implemented.

  • Coordinate upgrade timing with Syncfish to help identify and address any potential issues before deployment.

Objective: Ensure the new JDisc version is tested, and compatibility issues are identified before the upgrade proceeds.

3. Test Jobs and CIDR Filtering

Best Practice: Enable the CIDR filter for all Test jobs by default, unless Syncfish explicitly requests otherwise.

  • Ensure the CIDR filter is enabled when configuring and running Test jobs.

  • Apply the filter to limit the scope and size of the Test job.

  • Only disable the CIDR filter when specifically requested by Syncfish.

  • Be aware that running Test jobs without the CIDR filter may significantly increase execution time and, in some cases, result in jobs running for several hours.

Objective: Reduce Test job execution times, limit unnecessary processing, and improve testing efficiency.

4. Compliance and Review

All personnel involved in JDisc upgrades and Test job execution should follow these guidelines. Any deviation from these practices should be agreed upon with Syncfish before proceeding.

Following these best practices will help ensure a controlled upgrade process and more efficient Test job execution.