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-47874] Support multiple repositories in multi-branch pipeline #262

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

hint66
Copy link

@hint66 hint66 commented Jul 23, 2021

As described in the issue JENKINS-47874 I would like to be able to configure multiple repositories with same branch names in a single multi branch project.

To allow this setup, a new BranchProperty is added which allows the configuration of a pattern that is used to optionnaly customize the branch name in jenkins.branch.Branch#getName().

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@KalleOlaviNiemitalo
Copy link

Could add a help file that explains this is intended for disambiguating when there are multiple branch sources with possibly overlapping branch names.

@harakka
Copy link

harakka commented Sep 16, 2022

Are you still working on this feature or has there been any feedback from the project through other channels? I've run into this issue as well, and this feature would be very useful.

@hint66
Copy link
Author

hint66 commented Sep 16, 2022

Hello, I'm updating the fork from time to time, but ended up going in a different direction.
I've never had any feedback, so maybe I'm missing something (It's my first try of submitting a PR)

@jglick
Copy link
Member

jglick commented Dec 15, 2022

From a five-second glance, the code is probably OK, but the motivation remains unclear and I would suggest the PR and the Jira issue be closed as “will not do”. Whatever the ultimate goal may be, there is probably a more straightforward way to accomplish it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants