MultiJob Jenkins plugin is deprecated (Switch to pipelines?)
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
https://github.com/jenkinsci/tikal-multijob-plugin
Deprecation Note
This plugin was very popular for many years, but since most of Jenkins usage now is based on Jenkins Pipeline, and the 'parallel' step along with 'BlueOcean' can basically do whatever this plugin does, it is no longer in Tikal's radar.
Also, we published the parallelPhase library class that can do in pipelines what the plugin does.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked tikal-multijob-plugin deprecation note and src/tci/pipeline/parallelPhase.groovy, then inspect how this repository’s Jenkins jobs use MultiJob. The issue does not name a Node.js build file, job, or test, so confirm the migration scope and define completion as replacing affected usage with a pipeline equivalent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100