New in v2.3.0 FRS file upload & download · Build reporting with changelog · Multibranch pipeline support · Single sign-on

GForge Jenkins Plugin

Jenkins builds, tracked in GForge. Automatically.

Install once. Every build your Jenkins jobs run against GForge-hosted repos posts its result, output, and changelog to GForge — with no changes to your Jenkinsfiles.

Build status, console output, and Git changelog posted to GForge on every build
Download dependencies from GForge FRS before the build, upload artifacts after
Build events appear in your GForge project activity feed in real time
Supports Freestyle, Pipeline, and Multibranch Pipeline jobs

Download the Plugin Read the Docs →

Jenkins — Pipeline Console

[Pipeline] { (Checkout)

Cloning: https://next.gforge.com/git/my-project

✓ GForge activity posted — my-project #42 started

[Pipeline] { (Build)

[INFO] BUILD SUCCESS — 3.4 s

[Pipeline] { (Test)

Tests run: 47, Failures: 0, Errors: 0

[Pipeline] { (Publish)

gfrsUpload: my-app-2.3.0.jar → GForge FRS

[Pipeline] End of Pipeline

✓ Build #42 result posted → SUCCESS

✓ Changelog synced — 3 commits

✓ my-app-2.3.0.jar uploaded to FRS release 2.3.0

Download

Get the GForge Jenkins Plugin

A single .hpi file. Upload it to Jenkins and you’re done.

GForge Jenkins Plugin

gforge-jenkins-plugin.hpi

v2.3.0

SHA256: d353235ef3bc0dfb…

Download

Integration

Build once. GForge knows instantly.

The plugin hooks into Jenkins at the system level. Any job whose Git remote points to your GForge instance automatically posts its build events and results — no Jenkinsfile changes, no per-job configuration.

Jenkins

any job type

→

HTTPS

GForge Plugin

auto-detects repos

→

REST API

GForge Next

self-hosted or cloud

Automatic repo detection

No per-job setup. The plugin checks each job’s Git remote at build time. If it points to your GForge instance, it reports. If it doesn’t, it stays silent — zero impact on non-GForge jobs.

Complete build data

Every build posts its result, full console output, and Git changelog with commit SHAs. Everything you need for an audit trail, stored in GForge alongside the project it belongs to.

Every job type supported

Freestyle, Declarative Pipeline, Scripted Pipeline, and Multibranch Pipeline jobs all work out of the box. Multibranch jobs resolve the branch SCM source automatically at build time.

Jenkins build result in GForge showing completion time, SUCCESS status, external Jenkins link, build output tab, and change log tab

Build result in GForge — status, output, and changelog in one view

Jenkins build badge appearing in a GForge ticket activity feed next to the commits that triggered the build

Build badge in your ticket’s activity feed — next to the commits that triggered it

Features

Everything connected. Nothing to configure per job.

Install the plugin at the Jenkins system level and it covers every job that uses a GForge-hosted repository — automatically.

Automatic Build Reporting

Every build completion posts its result, console output, and Git changelog to GForge. The build record includes the Jenkins URL so your team can jump to the full log in one click.

Activity Feed Integration

Build start events appear in your GForge project activity log before the build finishes. Your team sees what’s in flight without ever leaving GForge.

FRS File Sync

Use gfrsDownload to pull dependencies from a GForge FRS release before the build. Use gfrsUpload to publish your artifacts back when it’s done — with collision handling built in.

Single Sign-On

Configure Jenkins to authenticate against your GForge instance. Your team uses the same credentials for both — no separate Jenkins user management, no passwords to sync.

Pipeline DSL

File releases, automated in your Jenkinsfile.

Build reporting is fully automatic. For FRS file transfers, add a single step to your pipeline — or use the Freestyle build step UI. Both work exactly the same way.

Two steps. One before the build, one after.

Add either or both to any Declarative or Scripted Pipeline. In Freestyle jobs, chained dropdowns populate projects, packages, and releases from your GForge instance automatically — no IDs to look up manually.

Before the build — gfrsDownload

Pull files matching a glob pattern from a GForge FRS release into your workspace. Optionally fail the build if nothing matches.

gfrsDownload(
  credentialsId: 'gforge-creds',
  project:       'my-project',
  packageId:     '12',
  releaseId:     '45',
  fileGlob:      '*.jar',
  failOnNoMatch: true
)

After the build — gfrsUpload

Upload workspace files matching a glob to a GForge FRS release. Handle collisions with add, replace, or skip.

gfrsUpload(
  credentialsId: 'gforge-creds',
  project:       'my-project',
  packageId:     '12',
  releaseId:     '45',
  fileGlob:      'target/*.jar',
  onCollision:   'replace'
)

Use Cases

One plugin, every workflow.

From release automation to compliance audit trails.

Release Management

Publish artifacts straight to GForge FRS

When your build produces a .jar, .war, or any other artifact, upload it directly into a named GForge FRS release — versioned, accessible, and linked to the build that produced it.

// Jenkinsfile post block post { success { gfrsUpload( credentialsId: ‘gforge-creds’, project: ‘my-app’, releaseId: ’45’, fileGlob: ‘target/*.jar’, onCollision: ‘replace’ ) } } ✓ my-app-2.3.0.jar → GForge FRS release 2.3.0

Compliance & Audit

A permanent record of every build

Every build result — status, full console output, and Git changelog with commit SHAs — is stored in GForge automatically. Teams that need traceability between code changes and build outcomes get it without extra tooling.

GForge build record — created automatically Build: my-project #42 Result: SUCCESS Completed: Jun 10, 2026 10:35 AM Changelog: commit a4f9c2d Fix null pointer in auth handler commit 3b8e1f0 Update session timeout config

Unified Activity

Jenkins events in your GForge project feed

Build start and completion events appear in the GForge project activity log alongside commits, issue updates, and file releases. Your team sees the full picture in one place.

GForge project activity feed ✓ my-project build #42 completed Passed my-project #42 → gforgegroup.com/builds/job/… tbibbs committed 4e9ecd2b [#65231] Fix auth timeout issue

CI/CD Automation

Pull build dependencies from GForge FRS

Store versioned dependencies, build tools, or config files in a GForge FRS release and pull them into your workspace before the build. No external artifact servers required.

// Jenkinsfile — fetch shared dependencies stage(‘Prepare’) { steps { gfrsDownload( credentialsId: ‘gforge-creds’, project: ‘shared-libs’, packageId: ‘8’, releaseId: ’31’, fileGlob: ‘*.jar’, failOnNoMatch: true ) } }

Quick Start

Up and running in four steps.

Install the plugin, point it at your GForge instance, and every build against a GForge repo starts reporting automatically.

1

Download the .hpi file

Use the Download button above. You’ll get gforge-jenkins-plugin.hpi.
2

Upload to Jenkins

Go to Manage Jenkins → Manage Plugins → Advanced → Deploy Plugin. Upload the .hpi file and restart Jenkins when prompted.
3

Set your GForge URL

Add GFORGE_URL to your Jenkins system environment variables, pointing at your GForge instance base URL.
4

Attach credentials

Add a Username/Password credential in Jenkins and attach it to the Git SCM of any job using a GForge-hosted repo. The plugin detects it from there and reports automatically.

Jenkins system environment variables

# Required — your GForge instance base URL GFORGE_URL=https://your-gforge-instance.com # Optional — restrict login to org members only GFORGE_ORG=your-org-name # Optional — max console output chars sent to GForge # default is 4096 GFORGE_MAX_DATA_SIZE=4096 # After restart: attach a GForge credential to any # job’s Git SCM — the plugin does the rest.

FAQ

Common questions

Things people ask before they install.

Does it work with a self-hosted GForge instance?

Yes. Set GFORGE_URL to your instance’s base URL and that’s all the plugin needs. It talks directly to your GForge installation — there is no dependency on gforge.com or any cloud relay.

Which Jenkins job types are supported?

Freestyle, Declarative Pipeline, Scripted Pipeline, and Multibranch Pipeline jobs are all supported. For Multibranch jobs the plugin resolves the branch SCM source automatically — no extra configuration per branch is needed.

Do I need to change my Jenkinsfiles to get build reporting?

No. Build start and build result reporting are fully automatic — the plugin hooks into the Jenkins build lifecycle and fires without any Jenkinsfile changes. The gfrsDownload and gfrsUpload pipeline steps are optional and only needed if you want FRS file transfers.

What data is sent to GForge?

On build start: the project name and build number. On build completion: the result (SUCCESS / FAILURE / UNSTABLE / ABORTED), console output (truncated to GFORGE_MAX_DATA_SIZE characters, default 4096), the Git changelog with commit SHAs and authors, and the Jenkins build URL. No source code is ever transmitted.

What are the minimum requirements?

Jenkins 2.479.1 or later, JDK 17 or later, and a Git SCM configured to use a GForge-hosted repository. The plugin activates only for jobs whose Git remote URL contains the configured GFORGE_URL — it has zero impact on jobs that don’t use GForge.

Your Jenkins builds belong in GForge.

Install once. Every build against a GForge repo reports automatically — no Jenkinsfile changes, no per-job setup.