Git Sources

Git sources let you connect a git repository to Paquetier so that packages are built automatically when new tags are pushed or commits land on a branch.

How It Works

1. Paquetier polls the git repository on a configurable schedule.
2. When a new tag or commit is detected (based on the trigger type), it clones the repository.
3. It runs R CMD build to produce a source tarball.
4. The tarball is ingested into all linked target repositories.
5. Optionally, binary packages are built via the bincraft R package.

Build progress is streamed in real-time to the web UI via server-sent events (SSE). Build logs are persisted and can be viewed or downloaded later.

Adding a Git Source

1. Navigate to Git Sources in the sidebar.
2. Click Add Git Source.
3. Configure the source:

Setting	Description
Git URL	The repository URL (HTTPS or SSH)
Credential	Select a git credential for private repos, or “None” for public repos
Trigger	When to build: new tags, branch commits, or manual only
Tag Pattern	Glob pattern for tag triggers (e.g. v*, *). Only applies to tag triggers.
Branch	Branch name for branch triggers (e.g. main)
Poll Interval	How often to check for changes (minimum 5 minutes, default 15 minutes)
Subdirectory	Path to the R package source within the repository (optional)
Target Repositories	Which Paquetier repos should receive the built packages
Build Binaries	Whether to also build platform-specific binary packages

4. Click Add Source.

Trigger Types

Tag Triggers

Builds are triggered when new git tags matching the configured pattern are created. This is the recommended approach for release workflows.

Branch Triggers

Builds are triggered when new commits appear on the configured branch. Useful for nightly or development builds.

Manual Triggers

No automatic polling. Builds can only be triggered manually via the Build Now button in the UI or the API.

Monitoring Builds

Navigate to Builds to see the build history. Each build shows:

• Status — Pending, running, completed, or failed.
• Source — Which git source triggered the build.
• Ref — The git tag or commit that was built.
• Duration — How long the build took.
• Log — Full build output, viewable in the UI or downloadable.

Failed builds can be retried with the Retry button.