Jenkins and CI/CD Integration, On the Task Itself
See the build and pipeline status of the work item you are looking at. Create branches straight from a task, and stop pull requests merging before the work is actually ready.
Available in the Self-Hosted edition - runs on your own servers
This capability is available in the Self-Hosted (on-premise) edition. It is not part of the Cloud edition today.
What is CI/CD integration in project management?
CI/CD integration connects your build and deployment pipelines to the work items they belong to, so a project manager can see whether the code for a task actually built and passed. Orangescrum reads build status from Jenkins, GitLab CI, GitHub Actions, and Bitbucket Pipelines, links it to the task by its work item identifier, and can block a pull request from merging until the task reaches the right status.
Why delivery status is never clear
Connect your pipeline to your work items
Jenkins build status
Pull build and job status from Jenkins and show it against the work item the change belongs to.
Pipeline status from every provider
The same view covers GitLab CI, GitHub Actions, and Bitbucket Pipelines, so mixed toolchains still give one answer.
Create branches from a task
Start a branch directly from the work item on GitHub, GitLab, or Bitbucket, with a consistent name that links back.
Pull request gating
Stop a pull request being approved or merged until the linked work item reaches the workflow status you require.
Status write back
Orangescrum writes a commit status back to the provider, so the gate is visible where developers already work.
Work item linking
Branches and commits reference the task by its identifier, so the connection is made automatically.
Webhook ingestion
Pipeline events arrive by webhook and are normalised, so every provider is handled the same way.
Repository mapping
Map repositories to projects once, and everything from those repositories lands in the right place.
How it fits together
For teams running real pipelines
Which edition includes what
| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |
|---|---|---|---|
| Jenkins build status | ✗ | ✓ | ✗ |
| GitLab CI, GitHub Actions, Bitbucket Pipelines status | ✗ | ✓ | ✗ |
| Create branches from a task | ✗ | ✓ | ✗ |
| Pull request gating by workflow status | ✗ | ✓ | ✗ |
| Commit status write back | ✗ | ✓ | ✗ |
| Git repository sync and issue linking | ✓ | ✓ | ✗ |
Jenkins integration FAQ
Does Orangescrum integrate with Jenkins?
Yes. Orangescrum reads build and job status from Jenkins and shows it against the work item the change relates to, so you can see whether the code for a task actually built and passed without leaving the project tool.
Which edition includes the Jenkins integration?
The DevOps and CI/CD layer, including Jenkins, is available in the Orangescrum Self-Hosted edition. The Cloud edition supports Git repository sync and issue linking.
Which other CI tools are supported?
The same DevOps layer covers GitLab CI, GitHub Actions, and Bitbucket Pipelines, so teams with a mixed toolchain still get one consistent view of pipeline status.
Can I create a branch from a task?
Yes. You can create a branch on GitHub, GitLab, or Bitbucket directly from the work item. The branch name carries the task identifier, so commits and pull requests link back automatically.
What is pull request gating?
Pull request gating stops a pull request being approved or merged until the linked work item has reached a workflow status you allow. It prevents work merging while the task is still in review or failing QA.
How does Orangescrum know which task a build belongs to?
Branches and commits reference the task by its work item identifier. Orangescrum reads that identifier and links the pipeline result to the right task.
Do I need to change my pipeline?
No. Pipeline events arrive by webhook and are normalised on the Orangescrum side, so each provider is handled the same way without rewriting your build scripts.
Does this work behind a firewall?
Yes. Because this is the self-hosted edition, Orangescrum and your Jenkins server can both sit inside your own network.
Connect your pipeline to your projects
The DevOps and CI/CD layer is included in the Orangescrum Self-Hosted edition, running entirely on your own infrastructure.