Import project items

Project items are added to a project one at a time, or many at once with bulk import.

Add a Project Item

1. Open the project.
2. Click Add → Project Item.
3. Select the Named Configuration (integration), repository, and branch you want to scan.
4. Click Add Project Item.

You can add the same branch more than once, or add different branches of the same repository.

Add Project Items in Bulk

Use bulk import when you need to attach many repositories from one integration without adding them one by one.

1. Open the project.

2. Click Add → Project Items (bulk).

3. In the dialog, select the Named Configuration (integration).

4. Optionally, upload a CSV or JSON file that lists the repositories from that integrated platform you want to import as project items. Matching repositories will be pre-selected in the next step.

5. Click Next: Select.

6. Select repositories

   KvantumCI loads the repositories available for the chosen integration. Adjust the selection as needed:

   • Use filters to narrow the list.
   • Manually mark or unmark individual repositories.

7. When the selection is ready, click Next: Configure.

8. Configure import

   In Configure import, set how the selected repositories should be onboarded:

   • Branches: use the default branch for each repository, or provide a custom list of branches.
   • Skip already onboarded repositories
     • On: skip repositories that are already project items (avoid duplicates).
     • Off: add a new project item when the branch is new (even if the repository is already onboarded under another branch).
   • Run verification immediately: start one verification run for each newly created active project item immediately after import. Duplicates and failed imports do not request runs, and items over quota are skipped.

9. Click Next to continue to Preview.

10. Preview and import

    In Preview, review what will be imported. When you are satisfied, click Import N project items (the button shows how many project items will be added). KvantumCI imports them into the project as project items.

    tip

    If you only need one or a few project items, use Add → Project Item instead.

Bulk import limits

Limit	Value
Repositories in one bulk import	10,000
Repositories imported without a background job	500
Branches per repository	5
Length of a branch name	255 characters
Rows in an uploaded CSV or JSON file	50,000
Bulk imports running at the same time, per organization	10

Branch names must be unique within a single repository entry. If you start an eleventh bulk import while ten are still running, the request is refused until one of them finishes.

Immediate and background imports

Up to 500 repositories are imported in one step, and the per-repository outcome is shown as soon as the import finishes.

Above 500 repositories, the import runs as a background job. You get a job to follow rather than an immediate result, and the page reports progress while the job works through the repositories in batches. A running job can be cancelled, and it stops at the next batch boundary, so repositories already imported stay imported. If a batch hits a temporary problem, the job retries it up to five times with an increasing wait between attempts before it gives up. Completed, failed and cancelled jobs stay available for 30 days, and the job list shows the last 7 days.

File format

The file you upload lists the repositories to pre-select, and it is read in your browser rather than uploaded to the server.

• CSV must have a header row containing repository and branch. The optional provider and project columns help disambiguate a repository whose name occurs more than once.
• JSON must be an array of objects, each with a repository and a branch.

A repository is matched against the repositories discovered for the chosen integration by full name, short name, or URL, ignoring case and a trailing .git. A row whose provider does not match the selected integration is left out. If a file lists more than 5 branches for one repository, the extra branches are reported as dropped.

Duplicate handling

The Skip already onboarded repositories setting decides what happens when a repository is already in the project:

• On: the repository is skipped entirely, whichever branches you selected.
• Off: only the exact repository and branch combinations that already exist are skipped, and any genuinely new branch is added.

Rows that repeat within the same import are always skipped, whatever this setting is.

Results and partial failures

A bulk import is never all or nothing. Every repository and branch combination gets its own outcome, either created, skipped as a duplicate, or failed with a reason. A row that fails does not stop the rest of the import.

Your subscription plan's project item allowance is applied as the import runs. Once the allowance is used up, each remaining row is reported as failed with a limit-reached reason while everything imported up to that point is kept. See Subscription plans for the allowance on your plan.

Running verification after import

Starting a verification run as part of the import requires permission to run verifications. Verification is triggered only after the import itself has been saved, and only for project items that were actually created. It is best effort: if a run cannot be started for a repository, that is recorded against the row and the import still succeeds. Reasons you may see include the integration being disconnected, the repository being unavailable, a verification already running for that repository, and the verification quota being reached.

Removing a project item

To remove a project item, see Project management.