jenkinsci / jenkinsci/workflow-aggregator-plugin
[JENKINS-46451] Define additional GIT Repos in pipeline jobs for git-parameter-plugin
- Dominant language
- No language data
- Stars
- 225
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
We have several pipeline-jobs, which retrieve their script from a dedicated GIT repository.
Many of those jobs have a branch-name as input parameter, which is used in the pipeline. Right now, we have to use a text-parameter and enter the branch name manually, because the repository which contains the branches is not the same as the one which contains the pipeline scripts.
It seems, what we would need is either:
- The git-parameter-plugin allows to configure a repository as source for the parameter (instead of using the first one found or the one matching the repository-name)
- The Pipeline-Job allows to define additional repositories, which can be accessed by name
---
Originally reported by mcirikovic, imported from: Define additional GIT Repos in pipeline jobs for git-parameter-plugin
Raw content of original issue
We have several pipeline-jobs, which retrieve their script from a dedicated GIT repository.
Many of those jobs have a branch-name as input parameter, which is used in the pipeline. Right now, we have to use a text-parameter and enter the branch name manually, because the repository which contains the branches is not the same as the one which contains the pipeline scripts.
It seems, what we would need is either:
- The git-parameter-plugin allows to configure a repository as source for the parameter (instead of using the first one found or the one matching the repository-name)
- The Pipeline-Job allows to define additional repositories, which can be accessed by name
Contributor guide
Research direction
The issue names git-parameter-plugin and Pipeline-Job but no repository files, tests, or entry point. Start by determining whether the requested repository source belongs in git-parameter-plugin or Pipeline-Job, then define a supported configuration path and verify it for jobs using separate script and branch repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100