Bulk Editing Polling Interval for Repositories

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Bulk editing the polling interval for repositories is not possible and for instances with a high number of repositories this can become an extraneous manual operation.

Cause

Fisheye/Crucible currently does not provide that option via the Administration interface. More information can be found on the following feature request: FE-4205 - Possibility to change the interval of the default polling.

Resolution

It is possible to workaround the bulk editing by editing the config.xml file:

  1. Backup the FISHEYE_INST/config.xml file.

  2. Go to Fisheye/Crucible Administration > Repository Settings > Repositories.

  3. Select one repository (as example) by clicking on the repository name.

  4. Go to Updates.

  5. Uncheck the "Use the system default settings for updates" box.

  6. Change the value in "Polling Interval" or check the "Disable polling" box.

  7. "Save".

  8. Shutdown Fisheye/Crucible.

  9. Open the FISHEYE_INST/config.xml file for editing.

  10. Locate the section with the edited repository:

    1. If the polling interval has been defined (example 30 minutes), the following section has been added:

      1 <updater pollPeriod="30minute"/>

    2. If the polling interval has been disabled, the following section has been added:

      1 <updater pollPeriod="never"/>

  11. Find and replace for all repositories where these settings should be applied. Note: Repositories which were using the default setting will not contain the <updater> tag. In these cases the new settings should be inserted within the repository type tag. Example:

    1 <git location="file:///Repositories/Git/git_repository" renames="none" path=""><updater pollPeriod="never"/></git>

  12. Save and close the FISHEYE_INST/config.xml file.

  13. Start Fisheye/Crucible.

Updated on April 8, 2025
Platform
Data Center only
Product
Fisheye Data Center
On this pageSymptomsCauseResolution

Still need help?

The Atlassian Community is here for you.
Ask the Community