I have this same issue. I have three servers setup. One with Jenkins
1.609.3, 1.642.4, and 2.60.3. I can use this plugin on my 1.6 - 1.6
instances but not 1.6 - 2.0. Wonder if there is an issue with jenkins 2.0?
I also noticed that on my 1.6 > 1.6 instances it returns a 500 if I use
choice
that out, and it was not obvious to me.
>
> --
> Craig
>
>
> On Tue, May 24, 2016 at 3:34 PM, Matt Evans > wrote:
>
>> I have tried many ways to bring variable in scope to a function, can you
>> please clarify how the following code should be written to bring the
&
I have tried many ways to bring variable in scope to a function, can you
please clarify how the following code should be written to bring the
variable "BRANCH_TEST" in scope?
* def BRANCH_TEST = "master"*
* node {*
* deploy()*
* }*
* def deploy(){*
* echo env.BRANCH_T
Recently we changed our way of building branches. We use GIT and have scm
polling to build branches. First, we used to poll a specific branch name
(release/1.0). Now we use a regex (release/*). For example, instead of
having:
jenkinsJob1 that builds branch release/1.0
jenkinsJob2 that