Repositories
Repository refresh
Refresh explicitly selected repositories when due through Redmine's native changeset fetch mechanism.
Scheduling model
- Global enable switch and default interval
- Explicit enablement for each repository
- Inherited default, fixed interval, or manual-only mode
- Bounded batch size and manual Refresh now action
Configure repository refresh
- Install and verify the central runner, then open Configure → Scheduler → Repository refresh.
- Enable the feature globally and choose the default interval.
- For each repository, enable scheduling and choose Use default, a fixed interval, or manual-only operation.
- To change many rows, select a bulk interval, copy it into the repository rows with the bulk action, and then apply the settings. Changing the bulk selector alone does not save row values.
- Use Refresh now for an intentional immediate update and review its resulting status.
Status and resilience
Metadata includes next run, last run, status, message, lock, and consecutive failures. Failure backoff limits repeated attempts; inactive projects are skipped without losing configuration.
Diagnose a repository that is not refreshing
- Confirm the central scheduler has a recent successful completion.
- Confirm global repository refresh and the individual repository row are enabled.
- Check whether the project is active, the next run is due, a lock is active, or failure backoff postponed the next attempt.
- Read the stored message and verify the repository's local or remote location outside the plugin before retrying.
Size reporting
After a successful refresh, local repository size is shown in a sortable column. Remote repositories without local paths have no measured size, and orphaned metadata is removed with its repository.
The size value is refreshed only after a successful repository update. A blank size for a remote repository is expected and is not an error.
Default vs. bulk action: a bulk interval changes rows only after the administrator copies the selection and applies settings.
