Skip to content

πŸ› Jenkins: Deprecated jenkins@1.1.0 NPM packageΒ #4984

@CryptoRodeo

Description

@CryptoRodeo

Workspace

jenkins

πŸ“œ Description

The Jenkins plugins has a deprecated dependency that hasn't been updated in ~2 years (jenkins): https://www.npmjs.com/package/jenkins?activeTab=versions

➜  jenkins git:(main) βœ— pwd
/home/bramos/work/community-plugins/workspaces/jenkins
➜  jenkins git:(main) βœ— yarn why jenkins
β”œβ”€ @backstage-community/plugin-jenkins-backend@workspace:plugins/jenkins-backend
β”‚  └─ jenkins@npm:1.1.0 (via npm:^1.0.0)
β”‚
└─ @backstage-community/plugin-scaffolder-backend-module-jenkins@workspace:plugins/scaffolder-backend-module-jenkins
   └─ jenkins@npm:1.1.0 (via npm:^1.1.0)

I see that dependency being used in these files:
Jenkins-backend:

scaffolder-backend-module-jenkins:

Replacing this deprecated package might not be too difficult. It looks like we just use the Jenkins type from the deprecated package, but more investigation is needed.

πŸ‘ Expected behavior

The plugin should use a newer, supported npm package to replace the deprecated jenkins one.

πŸ‘Ž Actual Behavior with Screenshots

The plugin uses a ~2 year old, deprecated npm package that may have security issues.

πŸ‘Ÿ Reproduction steps

  1. Go to Jenkins workspace
  2. Run yarn why jenkins
  3. Confirm the package listed is the same deprecated one found here: https://www.npmjs.com/package/jenkins?activeTab=versions

πŸ“ƒ Provide the context for the Bug.

No response

πŸ‘€ Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find similar issue

🏒 Have you read the Code of Conduct?

Are you willing to submit PR?

Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions