Re: Multiple repository with git parameter plugin

2019-04-03 Thread stefanocog
Yes, I install this plugin https://wiki.jenkins.io/display/JENKINS/Multiple+SCMs+Plugin and use instead of "Git" into "Management source code" section Il giorno mercoledì 3 aprile 2019 11:43:26 UTC+2, Yair Sappir ha scritto: > > Hey there, > Did you manage to solve this issue? I'm having the

Re: Multiple repository with git parameter plugin

2019-04-03 Thread Yair Sappir
Hey there, Did you manage to solve this issue? I'm having the same problem.. On Monday, September 4, 2017 at 1:57:56 PM UTC+3, stefanocog wrote: > > Hi, i need get list of branch of two repository, i install git parameter > plugin and i've set the two repo into SCM section but i get always

Re: Multiple repository and git parameter plugin

2017-09-11 Thread Mark Waite
I don't know if the git parameter plugin should handle that use case or not. It is unexpected (to me) that it behaves differently on subsequent repositories than it does on the first repository. I wonder if you want multiple SCM's, each with a single repository, rather than a single SCM with

Re: Multiple repository and git parameter plugin

2017-09-11 Thread Tony Martinet
Hi, Thanks for your answer Mark, and sorry for the delay of mine. I played with the pipeline script, and it's a nice solution, but i feel it doesn't suit my need completely. I want to be able to build a firmware with new libraries or SDK without creating a branch on the FW. I think with

Multiple repository with git parameter plugin

2017-09-04 Thread stefanocog
Hi, i need get list of branch of two repository, i install git parameter plugin and i've set the two repo into SCM section but i get always branch list from the same repository for first, second i get "No GIT repository configured in SCM configuration" attach image: image_1: git parameter

Re: Multiple repository and git parameter plugin

2017-08-25 Thread Mark Waite
You might consider running all the configurations in parallel from a single pipeline script, rather than prompting the user for their choice of branch. You might create a single Jenkinsfile on the branch where the developer is working, then start the different configurations in parallel within