Sources
This is the third tab of the Manage Organization panel: one table with all of the organization's data sources, regardless of which project they are (or are not) assigned to.
Columns: Name, Data source, Project, Interval, Last data scan, Status, Actions.
Where the sources on the list come from
Code repositories appear on this list automatically, discovered during scanning by the connector attached to the plugin. Sources are the Git version control systems Q247 supports, that is GitLab, GitHub, Bitbucket, Gitea, Gerrit, Azure DevOps, and repositories added as Generic GIT. They cannot be added by hand from this panel.
Jira and Confluence integrations are added with the Assign Source button, choosing the right type in the "Choose a data source" field and providing Jira project keys or Confluence space keys. The same form is used to assign discovered repositories, and the full description of its three variants is in the Sources tab in the project details.
Scanning
The "Actions" menu on a repository offers two actions: Start scanning and Assign to project.
"Start scanning" opens the interval choice:
- Hourly
- Daily, with a choice of the time zone the scan should run in
The choice is limited to these two options; a cron-style schedule is not available. The "Last data scan" column shows the date of the last run, "Never" for sources not yet scanned.
For ongoing work we recommend the Daily interval. Q247 metrics describe days and weeks, so a daily refresh is fully sufficient, and a less frequent scan reduces the load on both the plugin and the repository itself.
The hourly interval is worth setting for the duration of a deployment check, so you do not have to wait until the next day to confirm data is coming in, then switch to daily after the first successful run.
Bulk actions
Every row of the table has a checkbox on the left, and the one in the header selects all rows matching the current search and filters, not only the visible page of the table. Selecting at least two sources reveals a bulk action bar above the table.
Two actions are available for sources: Start scanning and Assign to project. Both work the same way as in the "Actions" menu, with one difference: the settings from the window (interval and time zone, or the target project) apply equally to all selected sources. Q247 processes them one by one, without asking for confirmation on each one separately.
Bulk assignment to a project has the same effects as a single one, described in Projects: history moves together with the source, and repositories return to the pre-scan state. So select deliberately, because selecting the whole list after an imprecise search will also catch sources the change was not meant for.
Jira and Confluence integrations synchronize on a different rhythm, independent of this setting, so the Interval column shows "N/A" for them.
Editing and removing
Jira/Confluence sources can be edited (changing the project/space key, the assigned Q247 project, the Active/Inactive status) or removed directly from the "Actions" menu. Automatically discovered repositories can only be edited in terms of project assignment, the source itself is managed on the plugin side.
See also
- Projects: assigning a source to a specific project from its own level
- Connectors: Enterprise Plugin deployments that discover repositories
- Jira and Confluence: the other source types on this list