Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 Jenkins: Explain Custom JenkinsInfoProvider for new backend system #1461

Closed
2 tasks done
juu0000 opened this issue Oct 2, 2024 · 2 comments
Closed
2 tasks done
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed stale

Comments

@juu0000
Copy link

juu0000 commented Oct 2, 2024

Plugin Name

jenkins-backend

🔖 Feature description

We need a way to use Custom JenkinsProvider under the new backend system of Backstage.

🎤 Context

My jenkins is set up with scm and I can clearly see the job through the api call, but the default jenkins provider doesn't seem to be able to retrieve the information properly. I need a document that describes how to use a custom jenkins provider to resolve this and how to apply it to a new backend system.

and i want to know what type of jenkins pipeline can be used to the jenkins plugin exactly.

even i don't know how to set jenkins pipeline for viewing the jenkins plugin. this also need guide docs.

✌️ Possible Implementation

No response

👀 Have you spent some time to check if this feature request 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?

None

@juu0000 juu0000 added the enhancement New feature or request label Oct 2, 2024
@vinzscam
Copy link
Member

vinzscam commented Oct 8, 2024

yep, most likely we would need to add an extension point for configuring custom providers. Marking the issue as help wanted.

@vinzscam vinzscam added help wanted Extra attention is needed good first issue Good for newcomers labels Oct 8, 2024
Copy link
Contributor

github-actions bot commented Dec 8, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Dec 8, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed stale
Projects
None yet
Development

No branches or pull requests

2 participants