Skip to content

SCMExtensionConfigProperties

Name Environment Description Default value Notes
ontrack.config.extension.scm.catalog.enabled ONTRACK_CONFIG_EXTENSION_SCM_CATALOG_ENABLED Enabling the SCM catalog false
ontrack.config.extension.scm.mock.enabled ONTRACK_CONFIG_EXTENSION_SCM_MOCK_ENABLED Enables the mock SCM, which keeps repositories, branches, commits and issues in memory instead of talking to a real SCM. Disabled by default; always enabled in the dev profile (the value shown opposite is the one the documentation build runs with). Enable it only on demonstration or test instances - never on an instance tracking real deliveries, where it would let a project claim an SCM that answers with whatever anyone posted to it. Its data lives on the bean and does not survive a restart unless persistent is set. true
ontrack.config.extension.scm.mock.persistent ONTRACK_CONFIG_EXTENSION_SCM_MOCK_PERSISTENT Keeps the mock SCM's repositories in the database, so that its commits, issues, files and pull requests survive a restart. Disabled by default: tests create their mock data inside the test and would only pay for the writes. Set it on a long-lived instance configured with the mock SCM - a demonstration instance, or a development stack whose backend is restarted often - where losing the data means the change log of an already-seeded project fails until the next reset. What it writes is an implementation detail of the mock SCM and not a storage format to depend on. Has no effect unless enabled is set. false
ontrack.config.extension.scm.search.schedule ONTRACK_CONFIG_EXTENSION_SCM_SEARCH_SCHEDULE Interval between two indexations, in hours. PT1H
ontrack.config.extension.scm.search.scheduled ONTRACK_CONFIG_EXTENSION_SCM_SEARCH_SCHEDULED Enabling auto indexation true