We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
this plugin only support get jenkins info from one host
our company has two jenkins host for different public cloud service. but now this plugin only support get jenkins info from one host
No response
None
The text was updated successfully, but these errors were encountered:
The Jenkins plugin supports multiple Jenkins hosts with the instances configuration attribute. https://github.com/backstage/community-plugins/blob/main/workspaces/jenkins/plugins/jenkins-backend/config.d.ts#L37
instances
Does this not work for your use case?
Sorry, something went wrong.
The Jenkins plugin supports multiple Jenkins hosts with the instances configuration attribute. https://github.com/backstage/community-plugins/blob/main/workspaces/jenkins/plugins/jenkins-backend/config.d.ts#L37 Does this not work for your use case?
I just read the source code and know how to config instance in catalog-info.yaml file. the 'jenkins.io/job-full-name' should start with "${instance_name}:", is that right? this should be add in this readme file: https://github.com/backstage/community-plugins/blob/main/workspaces/jenkins/plugins/jenkins/README.md
No branches or pull requests
Plugin Name
jenkins
🔖 Feature description
this plugin only support get jenkins info from one host
🎤 Context
our company has two jenkins host for different public cloud service. but now this plugin only support get jenkins info from one host
✌️ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: