You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I was first playing with these tools I was trying to create a Multibranch Pipeline because that is what I was familiar with. When Jenkins tried "Cloning build tools to workspace" it was always inserting "null" for the organization within the repo url. Donovan informed me that he experimented with making MP work with the tools but in the end decided to stick with the GitHub Branch Source Plugin. I am requesting we document which Jenkins items are compatible with these tools.
The text was updated successfully, but these errors were encountered:
I guess there is one other thing on this topic. When you create a "Github Organization" item in Jenkins, does the name of the item have to be the exact name of the github organization that the tools are in? It seems to me like the cloning url was pulling the organization name from this item name. If that is true it would be worth documenting that as well.
Hey everyone,
When I was first playing with these tools I was trying to create a Multibranch Pipeline because that is what I was familiar with. When Jenkins tried "Cloning build tools to workspace" it was always inserting "null" for the organization within the repo url. Donovan informed me that he experimented with making MP work with the tools but in the end decided to stick with the GitHub Branch Source Plugin. I am requesting we document which Jenkins items are compatible with these tools.
The text was updated successfully, but these errors were encountered: