Prune Jenkins plugins on ci-release.nodejs.org
Open
Nobody has claimed this yet.
ci-release
never stale
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
Today I updated all plugins to their latest version, then had a quick look at the plugin list and disabled these (we should uninstall them if no issues were introduced):
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 by reviewing the Jenkins plugin list on ci-release.nodejs.org and the disabled plugins shown in the issue image. Check whether any problems followed the plugin update or disabling; done means uninstalling plugins that remain unnecessary without disrupting CI.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100